and you would not be allowed to delete a parent without also deleting children.<br><br><br><br><div class="gmail_quote">On Mon, Mar 23, 2009 at 11:24 AM, Victor Kane <span dir="ltr"><<a href="mailto:victorkane@gmail.com">victorkane@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Data integrity is understood as respecting the relationships between tables.<br>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.<div>
<div></div><div class="h5"><br>
<br><div class="gmail_quote">On Mon, Mar 23, 2009 at 11:00 AM, Ivan Sergio Borgonovo <span dir="ltr"><<a href="mailto:mail@webthatworks.it" target="_blank">mail@webthatworks.it</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Mon, 23 Mar 2009 09:34:57 -0400<br>
<div>Earnie Boyd <<a href="mailto:earnie@users.sourceforge.net" target="_blank">earnie@users.sourceforge.net</a>> wrote:<br>
<br>
</div><div>> > Of course data integrity is not just about content of tables.<br>
> ><br>
><br>
> This is why the issue I pointed you to is so important.<br>
><br>
> >> > - if you're using advanced features, you're constrained by<br>
> >> > concurrent writes, you can't afford data loss and you didn't<br>
> >> > invest too much in MySQL there are better engines to look at.<br>
> >><br>
> >> Out of curiosity, what would you suggest? No, I'm not looking to<br>
> >> leave MySQL but I always enjoy learning a little more about<br>
> >> databases.<br>
> ><br>
> > PostgreSQL... but really it depends on your needs.<br>
><br>
> If only ANSI syntax is used then it shouldn't really matter which<br>
> transactional DB is used as long is the engine supports ANSI<br>
> transactional syntax. A transactional DB would allow for less PHP<br>
> code to be needed and a benefit would be the amount of disk i/o would<br>
> be lessened.<br>
<br>
</div>yeah... but is putting the bar much higher in terms of requirements...<br>
that won't make InnoDB just default but required.<br>
And it is not just a matter of transactions of course.<br>
Once you're in that league you may exploit many other features...<br>
<br>
But still if you want to keep supporting MyISAM and you want the DB to<br>
take care of relational integrity and such if possible... you're going<br>
to do twice the work if you still want to support MyISAM and sqlite.<br>
<br>
Maybe in the future there won't be any good reason to have half-RDBMS<br>
around so support for half-RDBMS could be dropped... but right now<br>
MyISAM and sqlite have their use case, and somehow dropping support for<br>
2 out of 4 supported DB is not going to make DB abstraction any better<br>
right now.<br>
<div><div></div><div>--<br>
[ Drupal support list | <a href="http://lists.drupal.org/" target="_blank">http://lists.drupal.org/</a> ]<br>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br>