[support] MyISAM vs InnoDB

Victor Kane victorkane at gmail.com
Mon Mar 23 14:24:48 UTC 2009


Data integrity is understood as respecting the relationships between tables.
So, if there are several tables in a one to many relationship with the node
table, say, for a CCK based content type, if the node is deleted, then the
child records would also be deleted.

On Mon, Mar 23, 2009 at 11:00 AM, Ivan Sergio Borgonovo <
mail at webthatworks.it> wrote:

> On Mon, 23 Mar 2009 09:34:57 -0400
> Earnie Boyd <earnie at users.sourceforge.net> wrote:
>
> > > Of course data integrity is not just about content of tables.
> > >
> >
> > This is why the issue I pointed you to is so important.
> >
> > >> > - 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.
> >
> > If only ANSI syntax is used then it shouldn't really matter which
> > transactional DB is used as long is the engine supports ANSI
> > transactional syntax.  A transactional DB would allow for less PHP
> > code to be needed and a benefit would be the amount of disk i/o would
> > be lessened.
>
> yeah... but is putting the bar much higher in terms of requirements...
> that won't make InnoDB just default but required.
> And it is not just a matter of transactions of course.
> Once you're in that league you may exploit many other features...
>
> But still if you want to keep supporting MyISAM and you want the DB to
> take care of relational integrity and such if possible... you're going
> to do twice the work if you still want to support MyISAM and sqlite.
>
> Maybe in the future there won't be any good reason to have half-RDBMS
> around so support for half-RDBMS could be dropped... but right now
> MyISAM and sqlite have their use case, and somehow dropping support for
> 2 out of 4 supported DB is not going to make DB abstraction any better
> right now.
> --
> [ Drupal support list | http://lists.drupal.org/ ]
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.drupal.org/pipermail/support/attachments/20090323/02f4bd52/attachment.htm>


More information about the support mailing list