Xref: alice comp.databases.oracle.server:69984 Path: alice!news-feed.fnsi.net!netnews.com!feed1.news.rcn.net!rcn!newsfeed.stanford.edu!remarQ73!remarQ.com!supernews.com!remarQ69!not-for-mail From: "Andris Nestors" Newsgroups: comp.databases.oracle.server Subject: Changes in Null handling from 7 to 8 Date: Fri, 15 Oct 1999 13:31:32 +0100 Organization: RemarQ http://www.remarQ.com Lines: 25 Message-ID: <7u76m6$2j6$1@supernews.com> X-Trace: 939990534 VZAWCPIAR2D6DD43AC uk21.supernews.com X-Complaints-To: newsabuse@remarq.com X-Newsreader: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 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