From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Emil Rachovsky <zsevgymko(at)yahoo(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: [SQL] lost in system tables |
Date: | 2005-12-06 17:12:46 |
Message-ID: | 4843.1133889166@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-sql |
Emil Rachovsky <zsevgymko(at)yahoo(dot)com> writes:
> I am trying to find the equivalent of these two
> Sybase system columns :
> check_on_commit (Y/N) - Indicates whether INSERT and
> UPDATE commands should wait until the next COMMIT
> command to check if foreign keys are valid.
I think you are looking for the DEFERRABLE/DEFERRED option of foreign
key constraints.
> nulls (Y/N) - Indicates whether the columns in the
> foreign key are allowed to contain the NULL value.
> Note that this setting is independent of the nulls
> setting in the columns contained in the foreign key.
No such animal in the SQL standard --- though perhaps MATCH FULL
is approximately what you are looking for? Your description as
stated makes no sense at all; either the columns are allowed to
be null, or they're not.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2005-12-06 17:48:08 | Re: Memory Leakage Problem |
Previous Message | Luca Pireddu | 2005-12-06 16:34:59 | Re: lost in system tables |
From | Date | Subject | |
---|---|---|---|
Next Message | Harald Fuchs | 2005-12-06 17:15:24 | Re: Date Interval |
Previous Message | Michael Fuhr | 2005-12-06 17:09:02 | Re: Date Interval |