Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Changes in Null handling from 7 to 8

Re: Changes in Null handling from 7 to 8

From: Sybrand Bakker <postmaster_at_sybrandb.demon.nl>
Date: Fri, 15 Oct 1999 19:55:32 +0200
Message-ID: <940010146.23546.0.pluto.d4ee154e@news.demon.nl>


I am afraid Oracle UK is correct. I don't have them at hand, but I do remember Oracle stating in the release notes of 7.3 they were going to desupport handling empty strings as NULL. I have been working with a different variant of the Pro products, Pro*Pascal, and they Oracle also stated in the manual 'always use NULL indicators'

Hth,

--
Sybrand Bakker, Oracle DBA
Andris Nestors <andris.nestors_no-spam_at_ac.com> wrote in message news:7u76m6$2j6$1_at_supernews.com...
> We are upgrading from 7.3.4 to 8.1.5 on Solaris 2.6.
>
> When our Pro*C application is compiled optimised O4 against the 815
> libraries and run against an 815 instance, we get different null handling
to
> the exact same app compiled O4 against the 734 libraries and run against a
> 734 instance.
>
> Using 734, CHAR columns containing nulls are reliably mapped to a C char*
as
> \0.
>
> Using 815, sometimes the char* contains \0 but sometimes it contains
> garbage.
>
> Of course we can solve the problem by using null indicators across the
> board, but this would be large scale changes to the application.
>
> Has anyone else experienced this problem ? Is there a workaround ?
>
> I have contacted Oracle Support in the UK, but they say "sorry - use null
> indicators".
>
> Thanks for any help.
> Andris
>
>
Received on Fri Oct 15 1999 - 12:55:32 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US