Re: Oversight?

From: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Rod Taylor <rbt(at)rbt(dot)ca>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Oversight?
Date: 2003-08-12 15:25:31
Message-ID: 20030812082258.U11777-100000@megazone.bigpanda.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 12 Aug 2003, Christopher Kings-Lynne wrote:

> > > rbt=3D# ALTER USER rbt SET CONSTRAINTS ALL DEFERRED;
> > > ERROR: syntax error at or near "ALL" at character 32
> > > rbt=3D# ALTER USER rbt SET CONSTRAINTS =3D DEFERRED;
> > > ERROR: "constraints" is not a recognized option
> >
> > "SET CONSTRAINTS ALL DEFERRED" is a SQL-spec-mandated command syntax.
> > Any similarity to Postgres' "SET var = value" syntax ends with the
> > initial keyword.
>
> I assume his point is "how do we set all of a user's constraints deferred by
> default"?

I don't think that'd make all of a user's constraints deferred, I'd think
it would make all constraints that are deferrable deferred for that
user's transactions (as if the user did a set constraints all deferred at
the beginning of every transaction).

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Rod Taylor 2003-08-12 15:28:50 pg_dump and REVOKE on function
Previous Message Andrew Dunstan 2003-08-12 15:22:48 Re: reuse sysids security hole?