On Aug 17, 8:08 pm, DA Morgan <damor..._at_psoug.org> wrote:
> zigzag..._at_yahoo.com wrote:
> > On Aug 17, 5:23 pm, "David Portas"
> > <REMOVE_BEFORE_REPLYING_dpor..._at_acm.org> wrote:
> >> <zigzag..._at_yahoo.com> wrote in message
>
> >>news:1187385280.227081.226550_at_g4g2000hsf.googlegroups.com...
>
> >>> On Aug 17, 10:49 am, Matthew Harrison <m.harris..._at_craznar.com> wrote:
> >>> Any value you put in the field/variable is
> >>> not same thing as null.
> >> Agreed. Any value is not the same thing as null
>
> >>> In my view, Oracle's approach is the right approach.
> >> Huh? But Oracle's approach is that the empty string value IS the same thing
> >> as null!
>
> >> --
> >> David Portas
>
> > I was not aware of that, but I do not belive same applied to other
> > data types such as integer,
>
> Then you would be incorrect: It does.
>
> Though I wouldn't suggest inserting an empty string into a DATE column.
> --
> Daniel A. Morgan
> University of Washington
> damor..._at_x.washington.edu (replace x with u to respond)
> Puget Sound Oracle Users Groupwww.psoug.org- Hide quoted text -
>
> - Show quoted text -
Why did then Oracle developed host variables, indicator variables
etc. Keeping null indicator separate from the actual value is the
right approach. When I have to insert null in a column, either I do
not use that column in insert or use indicator variable (in PRO*C) or
null in PL/SQL. It has always worked for me. Oracle may have messed up
things but if a disciplined approach by keeping null indicator
separate from the actual value is followed all through the code,
things will still work.
Received on Fri Aug 17 2007 - 19:55:08 CDT
