On Mon, Sep 26, 2005 at 01:12:40PM -0700, [EMAIL PROTECTED] wrote:
> >If Oracle strips trailing spaces on the client side, is that a
> >configurable option? How would you insert significant trailing
> >spaces into a VARCHAR column if the client library strips them?
>
> The Oracle precompiler (PRO
>If Oracle strips trailing spaces on the client
side, is that a
>configurable option? How would you insert significant trailing
>spaces into a VARCHAR column if the client library strips them?
The Oracle precompiler (PROC) has an
option: CHAR_MAP=CHARZ
that allows retaining cobol's trailing
bl
>Does Oracle really munge data on the client side?
Or does it, like
>PostgreSQL, pass the host variable's value as-is to the server, and
>the server considers trailing spaces significant or not depending
>on the context?
The Oracle C preprocessor/client
library has an option to strip trailing bl
On Fri, Sep 16, 2005 at 12:00:59PM -0400, Bruce Momjian wrote:
> [EMAIL PROTECTED] 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
[EMAIL PROTECTED] 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 w
Fuhr <[EMAIL PROTECTED]>, pgsql-bugs@postgresql.org
Subject
Re: [BUGS] BUG #1862: ECPG
Connect, host variable trailing blanks
On Fri, Sep 09, 2005 at 11:02:31AM -0700, [EMAIL PROTECTED]
wrote:
> This would allow current behavior to be supported by ECPG and the
Postgres
> server,
On Fri, Sep 09, 2005 at 11:02:31AM -0700, [EMAIL PROTECTED] wrote:
> 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.
Which preprocessor are yo
ichael Fuhr <[EMAIL PROTECTED]>
cc
[EMAIL PROTECTED], pgsql-bugs@postgresql.org,
[EMAIL PROTECTED]
Subject
Re: [BUGS] BUG #1862: ECPG
Connect, host variable trailing blanks
Michael Fuhr <[EMAIL PROTECTED]> writes:
> If you think this behavior should be changed then propose
Michael Fuhr <[EMAIL PROTECTED]> 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 traili
On Wed, Sep 07, 2005 at 12:06:10PM -0700, [EMAIL PROTECTED] wrote:
> According to the documentation at:
> http://www.postgresql.org/docs/8.0/static/ecpg-connect.html
>
>EXEC SQL CONNECT TO :target USER :user;
>The last form makes use of the variant referred to above as character
>varia
Subject
Re: [BUGS] BUG #1862: ECPG Connect,
On Tue, Sep 06, 2005 at 09:02:47PM +0100, James Gray wrote:
> The problem that we are having involves a connect statement with host
> variables:
>EXEC SQL CONNECT TO :target AS :user
>
> Our problem is that we are passed Cobol strings which are blank padded.
> Our string strategy works fi
The following bug has been logged online:
Bug reference: 1862
Logged by: James Gray
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: Red Hat Enterprise Linux AS release 4 (Nahant Update 1),
Kernel 2.6.9-11.EL on an ia64
Description:ECPG Con
13 matches
Mail list logo
