On Mon, 23 Mar 2009 12:45:28 +0100 Daniel Carrera daniel.carrera@theingots.org wrote:
Ivan Sergio Borgonovo wrote:
Well, not yet anyway. http://drupal.org/node/301362
...
My point is:
- if you're not using "advanced" features and you're not constrained by concurrent writes MyISAM is good enough. I'd say MyISAM may be even better suited to Drupal than InnoDB. None of the two engines is famous for data integrity after all.
I thought the whole point of InnoDB *was* data integrity.
I'm really not a MySQL black belt so I've commented on the topic more than reasonable... but InnoDB should also have better performances for concurrent write. BTW I just learned you can't use geo-indexes on InnoDB...
Of course data integrity is not just about content of tables.
- if you're using advanced features, you're constrained by concurrent writes, you can't afford data loss and you didn't invest too much in MySQL there are better engines to look at.
Out of curiosity, what would you suggest? No, I'm not looking to leave MySQL but I always enjoy learning a little more about databases.
PostgreSQL... but really it depends on your needs. Drupal PostgreSQL support is not the same as MySQL support, especially in contrib but I won't get scared about it. Still you need to know what you're doing. Suggesting switching to PostgreSQL may have the same result of suggesting to switch to Linux to a Windows user. A lot of people cry in despair and will curse you... others will never come back... for many reasons...