> Hmmm, and maybe not. You can bind it as SQL_CHAR and it should then
> preserve the trailing spaces, though I am not sure how oracle will handle it
> on it's side.
>
> Ilya
I think it has to do with the external datatype used in OCIBindBy...:
For VARCHAR2, trailing blanks are stripped.
$sth-
2:45 PM
Subject: RE: DBI/DBD Oracle - chopping trailing spaces
It's not DBD::Oracle, it's the way Oracle stores varchar2 fields. It
trims
them.
Ilya
-Original Message-
From: Arjan van Ham
To: [EMAIL PROTECTED]
Sent: 9/18/01 12:54 PM
Subject: DBI/DBD Oracle - chopping trailing
It's not DBD::Oracle, it's the way Oracle stores varchar2 fields. It trims
them.
Ilya
-Original Message-
From: Arjan van Ham
To: [EMAIL PROTECTED]
Sent: 9/18/01 12:54 PM
Subject: DBI/DBD Oracle - chopping trailing spaces
I noticed that DBD-Oracle trims blanks at the end
p_results;
###
produced the following result:
'b', 'b', 'b'
'c ', 'c ', 'c '
'a ', 'a ', 'a '
3 rows
> Dong Wang
> Grand Central Networks
> [EMAIL PROTECTED]
-Original Me
I noticed that DBD-Oracle trims blanks at the end of a field inserted into a
VARCHAR2-type column, even though ChopBlanks is set to False. Is that expected
behaviour ?
It messes up FreezeThaw. I'am saving a frozen field in the database, but when the last
character is a blank, thaw complaints
