The following URL will take you to the CHAR vs. VARCHAR semantics
section in the PL/SQL developers guide.
As Tim says, use varchar2 if possible. If not possible, you should
closely study the following
http://tinyurl.com/mvfj
Jared
On Wed, 2003-09-10 at 03:29, Fermin Bernaus wrote:
Fermin,
You are running into the well documented behavior of the CHAR datatype. Use
VARCHAR2 instead if you wish to avoid those pitfalls.
Hope this helps...
-Tim
on 9/10/03 3:29 AM, Fermin Bernaus at [EMAIL PROTECTED] wrote:
Thank you all of you who answered to my first question.
No,
!
Fermin.
-Mensaje original-
De: Tim Gorman [mailto:[EMAIL PROTECTED]
Enviado el: miércoles, 10 de septiembre de 2003 16:50
Para: Multiple recipients of list ORACLE-L
Asunto: Re: Weird behavior with VARCHAR fields (was: ORA-01403 error,
Fermin,
You are running into the well documented
SQL and PL/SQL are not the same until Oracle 9. There are distinct
differences between the two in earlier releases.
I don't have an 8.0.3 version of Oracle but the following is the result
from 8.1.7:
SQL create table wb (c1 char(8));
Table created.
SQL insert into wb values('abcd');
1 row
Hi!
One more interesting issue with CHAR datatype is, that it is not *always*
padded with spaces as sometimes understood. When the CHAR field is NULL,
then no spaces are saved into row. But as soon as you update even one single
char into it, the full CHAR length is used for this field in a row.
