Re: Problem with joining char field to varchar2 field
- From: Tim Gorman <tim@xxxxxxxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 05 May 2004 07:42:30 -0600
Sorry, I should have thrown a "smiley" after the comment about the "bug" in
ANSI SQL; it was a response directed to the question about whether the
cause was a bug in Oracle or a bug in AIX...
As you can tell, I see the CHAR and NCHAR datatypes as problems to be
eradicated... :-)
on 5/5/04 3:31 AM, Natural Join B.V. at lex.de.haan@xxxxxxxxxxxxxx wrote:
> Hi Tim,
>
> allow me to elaborate a little here.
> if you are referring to what I think you are referring to, this is not an
> ANSI/ISO bug but rather a feature ;-)
>
> it is not a matter of what you are physically storing in your database, but
> rather a matter of comparison semantics when dealing with strings of different
> lengths -- the two options are: padded vs non-padded semantics.
>
> Cheers,
> Lex.
>
> PS: adding leading zero's to a numeric attribute does not change its value;
> adding trailing spaces to an alphanumeric attribute DOES change its value.
>
>> Warren,
>>
>> This is a bug with the ANSI SQL standard.
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Other related posts:
