Hello!
Sorry for the late answer, I am a little busy at the moment.
On Thu, 13 Sep 2007, Charles Jardine wrote:
> > Annoyingly for me I can argue it both ways in this case.
> > Here's a question for you: what happens when the returnd value is
> > NULL?
> > How can you distinguish that from an empty array?
> Hmmm... In this particular case, Oracle object "TABLE OF ...
> INDEX BY BINARY INTEGER" can't be NULL. As far, as I know, it's
> impossible in Oracle.
Be careful here. Nested table and varray types in PL/SQL can by null.
Googling
on 'Until you initialize it, a nested table or varray is atomically null'
leads to clear documentation of this.
Yes, you're right. Though in case of table "INDEX BY BINARY_INTEGER"
statement "IF mytable IS NULL " always fails.
> > With the current API you could do this:
> >
> > $sth->bind_param_inout(":mytable", \my $ary = [EMAIL PROTECTED] , 10 , ... )
> > die "got null" if !$ary;
> >
> > (I'll admit I've made that rather terse, but that's not the point
> > here.)
> Ok. I'll change docs in my patch.
Hey, don't give in so easily! You can still persuade me. I'm teetering
on the end.
Anyone else have any opinions?
Do any other databases support array types? Can they be NULL?
Oracle supports array types which can by NULL, both in PL/SQL and
in SQL.
I strong agree with Tim's position before he teetered.
Hmmm.. It seems you're right.
Bye. Alex.
