Re: Postgres vr.s MySQL- style differences?

From: Lukas Kahwe Smith <smith(at)pooteeweet(dot)org>
To: pgsql-advocacy(at)postgresql(dot)org
Subject: Re: Postgres vr.s MySQL- style differences?
Date: 2007-05-29 18:47:24
Message-ID: f3hsfr$17q7$1@news.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

David Fetter wrote:
> On Tue, May 29, 2007 at 07:26:51PM +0200, Lukas Kahwe Smith wrote:
>> Jim Nasby wrote:
>>
>>>> Yup, the tend to heavily rely on data integrity management on the
>>>> middle tier. Which by the way is not totally crazy, because you
>>>> need most of the data integrity rules on the frontend anyways, to
>>>> generate proper GUI's. Actually in non object-relational RDBMS
>>>> (which are the norm, PostgreSQL is special), you can never do your
>>>> full integrity management inside the database.
>>> Can you give an example of that, because I can't think of one,
>>> unless you're talking about integrity that has to lie outside the
>>> database (ie: if you're storing filesystem locations in the
>>> database).
>> Yes, but more trivially since like "is this a valid email address"
>
> This is where PostgreSQL really shines. You can create a DOMAIN
> constraint that checks whether an address is valid all the way up to
> checking whether it's accepted for delivery, although I'd imagine you
> wouldn't want to do that last. You can then use that DOMAIN all over
> your code.

I know! I know!
/me hugs PostgreSQL

Actually while thinking of an example for my previous post I simply used
the "email validation" example from Roberts pl/php talk.

regards,
Lukas

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message Josh Berkus 2007-05-30 19:51:57 Netbeans wants to interview PostgreSQL people about developer tools
Previous Message David Fetter 2007-05-29 18:33:55 Re: Postgres vr.s MySQL- style differences?