Re: Pro*C Indicator Variables (bug?)

In article <3alno0$md3_at_epicycle.lm.com>, Keith A. Overstreet <kao_at_etgroup.com> writes:
|> We're moving from 1.3 to 1.5 of Pro*C.
|>
|> The Pro*C manual says that "When MODE=ORACLE, ORACLE does not
|> issue and error if you SELECT or FETCH a null into a host
|> variable that is not associated with an indicator variable."
|>
|> That would seem to contradict the error message that we
|> are getting (i.e. ORA-01405: fetched column value is NULL").
|>
|> MODE= ORACLE is the default. We've even explicitly set it.
|>
|> This only occurs if you have used an indicator variable on
|> one of the variables in the select. It seems that if you
|> use no indicator variables, it works fine. But if you
|> use one, you have to do them all.
|>
|> Should this work this way?
|>
|> Environment: HP-UX 9.0; Oracle 7.0.16; Pro*c 1.5.10.1
|> --
|> Keith A. Overstreet
|> Enterprise Technology Group, Inc.

You should use indicator variables - it's a better method of coding. The manuals aren't quite correct here (this has been fixed for the 1.6 docs). You need to use DBMS=V6 as well as MODE=ORACLE to avoid the ORA-1405 error. Received on Mon Nov 21 1994 - 18:48:43 CET