Excerpts from Richard Broersma's message of vie nov 05 18:54:54 -0300 2010:
> On Fri, Nov 5, 2010 at 2:37 PM, Alvaro Herrera
> wrote:
>
> > Recent developments have turned it back into non-deprecated mode; it's
> > not going anywhere, and it needs to be fully documented.
>
> From what I recall,
Alvaro Herrera writes:
> Some time ago, CREATE CONSTRAINT TRIGGER was a deprecated command and it
> was slated for obsolence or removal.
> Recent developments have turned it back into non-deprecated mode; it's
> not going anywhere, and it needs to be fully documented.
> It seems to me that it ma
On Fri, Nov 5, 2010 at 2:37 PM, Alvaro Herrera wrote:
> Recent developments have turned it back into non-deprecated mode; it's
> not going anywhere, and it needs to be fully documented.
>From what I recall, there isn't anything in the trigger documentation
or CREATE CONSTRAINT TRIGGER documentat
Some time ago, CREATE CONSTRAINT TRIGGER was a deprecated command and it
was slated for obsolence or removal.
Recent developments have turned it back into non-deprecated mode; it's
not going anywhere, and it needs to be fully documented.
It seems to me that it makes more sense to merge its docume
I wrote:
> 4. Try to auto-update inside the backend. I don't have an exact
> proposal for how this would work, but I'm thinking in terms of having
> the conversion key off CREATE CONSTRAINT TRIGGER commands referencing
> one of the built-in RI_FKey_xxx trigger functions. The tricky part here
> is
Back when we agreed that we should treat CREATE CONSTRAINT TRIGGER as a
documented, non-deprecated user command, I made a change so that it
would use the specified name as the actual name of the trigger in
pg_trigger. Pre-8.3 releases would auto-generate sorta-unique names of
the form "RI_Constrai
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> While the REFERENCES privilege controls who can create foreign keys
> referring to one's tables, it seems you can evade it by using CREATE
> CONSTRAINT TRIGGER directly.
Good point.
> It seems we need to check the privilege on the table mentioned in
While the REFERENCES privilege controls who can create foreign keys
referring to one's tables, it seems you can evade it by using CREATE
CONSTRAINT TRIGGER directly.
This is the "slave" portion of a FK constraint I got from pg_dump:
CREATE CONSTRAINT TRIGGER "$1"
AFTER INSERT OR UPDATE ON "s
