4 ms·
> MySQL is much more than a “nosql with mature replication” Yes. It is, and the parent is saying why (despite the fact it had more features) it shouldn’t be tr
by dijit 7y ago
> MySQL is much more than a “nosql with mature replication”
Yes. It is, and the parent is saying why (despite the fact it had more features) it shouldn’t be treated as anything more than a nosql document store with mature replication.
FWIW I’ve used MySQL, MongoDB, Postgres, Cassandra and a plethora of others at huge scale and I cannot possibly be clearer:
MySQL is full to the brim of foot-guns;
storage specific behaviours, leaky transaction isolation and silent data corruption behaviours et al.
You CAN, absolutely navigate it well enough to never lose a bit or get bitten by any of its “weird” behaviours, but it requires that every person touching the database is very well versed in the entire documentation of the database.
That is why the parent is not spreading FUD, because MySQL as a technology should be approached with caution, and the fact that it looks like it’s working when it’s corrupting your data is the worst design consideration of the entire thing; which necessitates this behaviour and reinforces the myth that MySQL is not dangerous.
- idoubtit 7y ago> it shouldn’t be treated as anything more than a nosql document store with mature replication. For years, Windows NT claimed to have Unicode support, but what they called Unicode was in fact the UCS subset that used 2 bytes for each character. They still haven't adopted UTF-8 which is ubiquitous on the web. Windows uses NTFS which is a mess ridden by compatibility constraints. For instance, the recent releases of NTFS at last introduce a snapshot feature, but mounting the volume may destroy the snapshot. FAT was even uglier. Linux and BSD are fully compatible with many mature file systems, while Windows has few options. Windows should not be treated as anything more than a volatile UI with mature drivers. Windows is dangerous and everyone should switch to Linux or BSD (MacOS for the hipsters). /sarcasm As inconsistent and dangerous as it may be, MySQL is more than a nosql document store.
- jmchuster 7y agoisn't this comment non-sarcastically why all servers run on linux and not windows?
- jjeaff 7y agoHate to break it to you, but there is this thing called Windows Server. It's quite prolific. Estimated around 20% or more.
- throwawayntfs 7y agoCurious which many hidden gems the open source BSDs contain in the way of mature file systems, since I haven't encountered any in my travels so far. The only things I've had luck interoperating between the BSDs have been ISO9660, FAT32, and ext2. Windows has full support for the former two, and to be honest all of those are less-than-ideal.
- grumpydba 7y ago> Yes. It is, and the parent is saying why (despite the fact it had more features) it shouldn’t be treated as anything more than a nosql document store with mature replication. This is very unfair to innodb which is a mature enterprise level relational engine.
- dijit 7y agoInnoDB is very nice, especially when compared to myISAM. If this post only contained information regarding myISAM then there would be a lot to unpack and it would look like flaming. I think I’m being fair to innodb though. It’s not necessarily InnoDBs fault that it cannot handle schema changes in a transaction, or munges data if the column isn’t the right size, or that it fails a commit but overwrites data anyway. These are generally MySQL problems, and it doesn’t matter which storage engine you use.
- grumpydba 7y ago> or munges data if the column isn’t the right size Same behaviour as Ms sql server or sybase. Would you be so harsh with them? > it cannot handle schema changes in a transaction. Same behaviour for some cases on sql server and sybase. Also in MySQL 8 some schema changes are indeed atomic. You are being unfair as those limitations are perfectly fine to live with. > it fails a commit but overwrites data anyway. Please provide more information
- dijit 7y agoUgh, this is going to get tedious, you're obviously feeling defensive for some reason. Please try not to be. MSSQL does not munge data if the column is not equipped for it, I have no idea about sybase. You can test this easily by making an int column and putting a maxint+1 in.. it will tell you "NO" and not insert anything. MSSQL supports schema changes in transactions, fully, again, not sure about sybase. MySQL 8 might support it /sometimes/ but the major concern I had with this fact is that MySQL doesn't tell you it's going to break its transaction isolation. -- it just commits in the middle of your transaction and moves on. My final point is mitigated somewhat by MySQL "Strict" mode, which nobody enables. I have very limited internet but this video should explain/show the behaviour I'm referencing: https://www.youtube.com/watch?v=emgJtr9tIME https://www.youtube.com/watch?v=emgJtr9tIME
- nqzero 7y agoi'm looking for a test suite that is used to verify query isolation and correctness at high levels of concurrency. ie do you know of anything that you could run against both databases to quantitatively say that postgres is better in this regard than mysql ? or that would somehow highlight that it's more complicated to get compliance from one that the other, eg because the required SQL is more complicated