[development] Referential integrity -- finally?

[Dries Buytaert]

On 20 Jan 2007, at 17:19, Victor Kane wrote:
> In the year or so that I have been working with Drupal I can see
> indeed that "the Drupal way" is to solve our problems (and the need
> for referential integrity is key here) basing ourselves fully on GPL
> solutions; and in this sense the excellent PostgreSQL (a product some
> say even excels when compared to fully commercial products such as
> Oracle) perhaps should be brought more into the center of the picture,
> or elevated from its status as "also supported", this without demoting
> MySQL in any way. And I have put this philosophy into practice by
> filing issues where modules have not supported several PostgreSQL
> installations I have been responsible for.

Absolutely -- and for that we need to conquer the heart of PostgreSQL  
users.  As explained, they care a lot about these things.

Here is what a PostgreSQL person said to me:

> As someone who is about as deep as you can get in the postgresql
> community without being core :). This is what I would like to see.
>
> Truly normalized schema
> Every table must have a natural primary key
> Relational Integrity
> Removal of ilike searches. Use lower() = lower() it is faster

(I modified and stripped his/her mail to hide his identity -- he  
might have been OK with me forwarding the entire message but I  
haven't checked so ...)

--
Dries Buytaert  ::  http://www.buytaert.net/