From: | Enrico Sirola <enrico(dot)sirola(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pggeneral <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pgsql constraints and temporal tables |
Date: | 2007-12-14 16:27:48 |
Message-ID: | 4762AF04.8090703@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Tom!
Tom Lane ha scritto:
> Enrico Sirola <enrico(dot)sirola(at)gmail(dot)com> writes:
>> However, I'm facing a problem I'm not able to solve with postgresql:
>> usually updating or deleting time-varying data means to temporary
>> violate a constraint in a transaction but ensuring that at the end of
>> the transaction the table(s) is(are) in a consistent state, but this
>> seems impossible to do because trigger constraints are not deferrable.
> Use CREATE CONSTRAINT TRIGGER:
> http://developer.postgresql.org/pgdocs/postgres/sql-createconstraint.html
>
> (This statement has been there all along, but was marked as deprecated
> in pre-8.3 releases, for now-forgotten reasons.)
>
> regards, tom lane
ah! My fault! I created the triggers with "create constraint trigger",
but was misleaded by the documentation on constraints, that says
triggers are not deferrables.
Thanks for the help,
e.
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Hart | 2007-12-14 16:53:59 | Re: Hijack! |
Previous Message | Charles Mortell | 2007-12-14 16:25:47 | user name and password woes |