Re: migrating from sql server 2000 to oracle 9i-r2

From: Frank van Bortel <fvanbortel_at_netscape.net>
Date: Sat, 12 Mar 2005 14:09:40 +0100
Message-ID: <d0uphn$7oi$1@news5.zwoll1.ov.home.nl>

DA Morgan wrote:

>>
>> Yes, well, that was not the issue.
>> The issue was about '', not about NULL being NULL not being NULL:
>> BANNER
>> ----------------------------------------------------------------
>> Oracle9i Enterprise Edition Release 9.2.0.6.0 - Production
>> PL/SQL Release 9.2.0.6.0 - Production
>> CORE    9.2.0.6.0       Production
>> TNS for Linux: Version 9.2.0.6.0 - Production
>> NLSRTL Version 9.2.0.6.0 - Production
>>
>> hr_at_O920.CSDB01.CS.NL> select * from dual where null = '';
>> no rows selected
>>
>> hr_at_O920.CSDB01.CS.NL> select * from dual where null != '';
>> no rows selected
>>
>> Ergo: '' is treated as NULL. And THAT is NOT ansi compliant.

>
>
> What you did in 9.2.0.6 proves nothing as that is the way
> Oracle has always worked. It is your words alone that claim
> this behaviour non-compliant.
>
> So lets try this again ... Tom Kyte specifically states that it
> is compliant ... and I referenced the specific page of the
> specific book in which he did.
>
> So if you think Tom is wrong then I'd suggest rather than showing
> us SQL statements that prove nothing ... you specifically address
> where Mr. Kyte is incorrect.
>
> Me? I'm going to sit back with a scotch and watch.

Daniel,

maybe you should leave the scotch (and try an Irish...) :)

You and Thomas Kyte talk about NULLs - and you and Tom are correct (and I concur, too, by the way). But the issue was *not* about NULLs.

The issue was about empty strings (''). And according to the ANSI standard, '' is NOT NULL.
Oracle regards it as NULL, and thus is *not* ANSI compliant.

Makes sense now? We've had this discussion before.

-- 
Regards,
Frank van Bortel

Received on Sat Mar 12 2005 - 07:09:40 CST