Peter Eisentraut <[EMAIL PROTECTED]> writes:
> PUBLIC can be made less reserved easily. See patch below.
Well, we could do that, but this patch seems an ugly way to do it;
we have too many classifications of keywords already, and I don't
want to introduce another one.
I'd be inclined to make PUBLIC not a keyword at all, and instead have
the production grantee -> ColId do this in its action:
if (strcmp($1, "public") == 0)
create PUBLIC PrivGrantee node
else
create normal PrivGrantee node
An objection to this is that you couldn't make a user named "public"
(with the quotes), since PUBLIC and "public" would look the same to
the action ... but that seems like a good restriction anyway. I'd
be quite willing to tweak CREATE USER to forbid that name.
I suppose it's a judgment call which is uglier. Thoughts?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
