| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Jim(dot)Gray(at)Bull(dot)com |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ken(dot)Rosensteel(at)Bull(dot)com, Michael Fuhr <mike(at)fuhr(dot)org>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #1862: ECPG Connect, host variable trailing blanks |
| Date: | 2005-09-16 16:00:59 |
| Message-ID: | 200509161600.j8GG0xD14689@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Jim(dot)Gray(at)Bull(dot)com wrote:
> What do you think of an Postgres option that would enable stripping of
> trailing blanks from connect host variables when turned ON?
I would not support such an option. If we added flags for every single
thing that someone wanted, the system would be unusable.
> This would allow current behavior to be supported by ECPG and the
> Postgres server, but allow applications that need the behavior (like
> a Cobol/SQL preprocessor for Postgres), to make use of it.
>
> When I searched the mail archives, I found that others had run into
> this same problem, in this case with an ODBC driver:
> http://archives.postgresql.org/pgsql-interfaces/1998-08/msg00000.php
Just because Oracle does it doesn't mean we should.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Fuhr | 2005-09-16 16:31:53 | Re: BUG #1862: ECPG Connect, host variable trailing blanks |
| Previous Message | Pete Beck | 2005-09-16 15:13:14 | Re: BUG #1886: Bug in SQL parsing |