Re: DEFERRABLE NOT NULL constraint - Mailing list pgsql-general

From Gavan Schneider
Subject Re: DEFERRABLE NOT NULL constraint
Date
Msg-id 16462-1360179504-5939@sneakemail.com
Whole thread Raw
In response to Re: DEFERRABLE NOT NULL constraint  (Alban Hertroys <haramrae@gmail.com>)
Responses Re: DEFERRABLE NOT NULL constraint  (Albe Laurenz <laurenz.albe@wien.gv.at>)
List pgsql-general
On Wednesday, February 6, 2013 at 23:31,=20
00jkxma2vt@sneakemail.com (Alban Hertroys haramrae-at-gmail.com=20
|pg-gts/Basic|) wrote:

>On 6 February 2013 12:56, Chris Angelico <rosuav@gmail.com> wrote:
>
>>If you get into a taxi and ask
>>to be driven to New Zealand within the hour, no amount of begging will
>>get you what you want.
>>
>
>....Unless you get into a taxi in New Zealand.
>

   ....Which makes the request effectively NULL, planning to do=20
this makes it DEFFERABLE.


Taking a different tangent ...

Is there anything in the SQL standards about NOT NULL=20
constraints being deferrable?

To my mind we should not consider implementing non-standard=20
behaviour, but if something is in the standard I can't see why=20
it shouldn't be implemented, esp. when there is no compulsion=20
for it to be used.

Regards
Gavan Schneider

pgsql-general by date:

Previous
From: Wells Oliver
Date:
Subject: Re: Keeping historical record changes w/ triggers - best practices?
Next
From: Jeff Janes
Date:
Subject: Re: Keeping historical record changes w/ triggers - best practices?