<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On 20 Jan 2007, at 5:56 PM, Dries Buytaert wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px"><BR></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">When talking with people of the PostgreSQL community, for example, it is clear that they steer away from Drupal, because we don't take their industry serious.<SPAN class="Apple-converted-space"> </SPAN>By adding support for referential integrity, we're reaching out to people that know more about databases.<SPAN class="Apple-converted-space"> </SPAN>It wouldn't hurt to have some database experts in our community.</FONT></P> </BLOCKQUOTE></DIV><BR><DIV>Maintaining schemas is still a lot of work,. and i fear adding another layer of complexity to it will start making it unmanageable.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Oracle, MSSQL, db2, mysql, sql lite, postgresql.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>This means we're going to be doing essentially the same work 6 times over. And that's only for core, the majority of contrib</DIV><DIV>modules will still not work on other db's.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>I also seriously doubt that just adding referential integrity is going to draw lots of postgresql experts out of the ether..</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>--</DIV><DIV> Adrian</DIV><DIV><BR class="khtml-block-placeholder"></DIV></BODY></HTML>