From: | Peter Eisentraut <e99re41(at)DoCS(dot)UU(dot)SE> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] RFC: create/alter user extension |
Date: | 1999-11-13 13:38:03 |
Message-ID: | Pine.GSO.4.02A.9911131436450.606-100000@Val.DoCS.UU.SE |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 12 Nov 1999, Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > Is everyone okay with the following syntax:
> > CREATE USER username
> > [ WITH ID digits ]
> > ^^^^^^^^^^^^^^^^^^
>
> > The catch is that ID would have to be a new keyword and we'd have to live
> > with that for a long time. Other choices include:
> > * UID
> > * SYSID
> > * USESYSID
> > etc.
>
> I'd be inclined to go with UID or SYSID. In any case, since the new
> keyword is used in such a limited context, we could almost certainly
> still allow it as a ColId and thus not create any real compatibility
> problem.
I'm not sure about this distinction. Where would that be reflected in the
(parser) code?
-Peter
--
Peter Eisentraut Sernanders vaeg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1999-11-13 14:50:08 | Re: [HACKERS] Backend build fails in current |
Previous Message | Peter Eisentraut | 1999-11-13 13:36:31 | Re: [HACKERS] Backend build fails in current |