From: | Michael Glaesemann <grzm(at)seespotcode(dot)net> |
---|---|
To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
Cc: | Andrus <kobruleht2(at)hot(dot)ee>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Best way to prevent overlapping dates |
Date: | 2007-05-29 18:05:34 |
Message-ID: | 6B8BA6FB-DE6C-4BB3-AB44-C14CFB675D0F@seespotcode.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On May 29, 2007, at 12:41 , Jeff Davis wrote:
> "CREATE CONSTRAINT TRIGGER is used within CREATE TABLE/ALTER TABLE and
> by pg_dump to create the special triggers for referential
> integrity. It
> is not intended for general use."
>
> Is there harm in using constraint triggers outside of pg_dump? It
> seems
> like deferrable constraints would be useful for many applications, but
> the docs imply that it's a bad idea.
It's a PostgreSQL extension, so it's nonstandard, but my
understanding is that it's safe to use and there are no current plans
to make it go away. As long as you understand what you're doing, I
don't know of any problems with using CREATE CONSTRAINT TRIGGER. I've
asked similar questions in the past, so you might want to check the
archives.
Michael Glaesemann
grzm seespotcode net
> PS: Nice to meet you at PGCon. Hope you enjoyed it as much as I did!
It was good to meet you too, Jeff! Hope to see you at the next
gathering :)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-05-29 18:09:17 | Re: opclass for real[] |
Previous Message | Tom Lane | 2007-05-29 17:59:02 | Re: Best way to prevent overlapping dates |