From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: getting confused parsing ACLITEMS... |
Date: | 2003-08-10 03:26:57 |
Message-ID: | 20030810112610.Y98663-100000@houston.familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Seriously, I think there's a good case for banning a few characters in
> at least some names - like []<>'"~#*|\ , say
Why? They're allowed in all other identifiers. And what if someone
already has a database full of usernames with those chars? They wouldn't
be able to load their dump properly...
Chris
> andrew
>
> Tom Lane wrote:
>
> >Andreas Pflug <pgadmin(at)pse-consulting(dot)de> writes:
> >
> >
> >>Is it useful to allow these special chars at all? Seems this creates a
> >>lot of work, and most admins will probably stick to "normal" user names
> >>anyway.
> >>
> >>
> >
> >Well, the reason it's been left unfixed for so long is exactly that it
> >didn't seem pressing. But if Chris wants to do the work, I won't stand
> >in his way ...
> >
> >
> >
> >
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2003-08-10 03:43:32 | Re: getting confused parsing ACLITEMS... |
Previous Message | Christopher Kings-Lynne | 2003-08-10 03:24:39 | Re: getting confused parsing ACLITEMS... |