2 ms·
>> performance needs a very careful eye > Clearly implying that performance doesn't require a careful eye on MySQL This is highly ironic, since you later say:
by barrkel 12y ago
>> performance needs a very careful eye
> Clearly implying that performance doesn't require a careful eye on MySQL
This is highly ironic, since you later say:
> you suck at logic
Funny chap!
(My point was that all the extra features in PostgreSQL give you more solution space, but not all of the solution space is suited to your problem. You have to watch out you're using the specific features in a way that pays off. Whereas MySQL is a bit like a hammer; you need to shape your problem like a nail, otherwise you won't be able to hit it at all. But when you do hit it, it mostly works. It's not a precision instrument though.)
>> makes it easy to do silly things, like turn off referential integrity in a slow query to boost performance.
> Which is really misleading, because it ships with most of that stuff off.
MySQL ships with referential integrity turned on - InnoDB is the default back end. Care to explain more?
(Personally, I wouldn't use MyISAM for my phone book, never mind in production.)
- noehp 12y ago> But when you do hit it, it mostly works. Except that this is not even slightly true. See: join performance, sub-query performance, etc. > MySQL ships with referential integrity turned on - InnoDB is the default back end. Care to explain more? This is... just wow. Wow. I can't even believe that you think 'Innodb is the default back end' == all integrity is present. That's so wrong it's... we're not even having the same conversation. Wow. You're shockingly stupid, even for the Internet. Wow.
- deleted 12y ago[deleted]
- noehps 12y ago" InnoDB is the default back end" This comment reveals that you're utterly and completely ignorant. If you think InnoDB treats your data with respect by default, you've clearly never actually paid close attention to anything.