| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Fuhr <mike(at)fuhr(dot)org> |
| Cc: | Jim(dot)Gray(at)Bull(dot)com, pgsql-bugs(at)postgresql(dot)org, Ken(dot)Rosensteel(at)Bull(dot)com |
| Subject: | Re: BUG #1862: ECPG Connect, host variable trailing blanks |
| Date: | 2005-09-09 04:15:24 |
| Message-ID: | 255.1126239324@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Michael Fuhr <mike(at)fuhr(dot)org> writes:
> If you think this behavior should be changed then propose it on
> pgsql-hackers and discuss it with the developers.
I doubt we'll consider changing it. If I haven't missed any of the
details, the critical points here are
(1) User names containing trailing (or embedded) spaces are legal.
Not a very good idea maybe, but legal both per SQL spec and per
our historical practice.
(2) Making ECPG strip trailing spaces would render it unable to
connect as such a user.
I don't think ECPG has any business deciding that trailing spaces are
insignificant. If that's the case in your application environment,
fine: strip the spaces at the application level. But don't expect a
general-purpose library to make that policy choice for you.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sijin MS | 2005-09-09 07:54:05 | BUG #1870: Insertion problem |
| Previous Message | Michael Fuhr | 2005-09-09 03:28:40 | Re: BUG #1862: ECPG Connect, host variable trailing blanks |