| From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(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 14:47:28 |
| Message-ID: | Pine.LNX.4.33.0308120846370.3756-100000@css120.ihs.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"?
But constraints aren't really per user, are they? I can see wanting to
set all of a table's contraints / dependent table constraints to deferred,
but a user's constraints doesn't make much sense to me.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-08-12 14:59:13 | Re: reuse sysids security hole? |
| Previous Message | Andrew Sullivan | 2003-08-12 14:47:05 | Re: Farewell |