Binding an undef should work and be treated as a NULL. Probably a bug in your code or the driver. But you didn't say which driver.
Tim. On Wed, Jul 10, 2002 at 11:14:03AM -0400, Phil R Lawrence wrote: > When I unwittingly try to bind an undef value, it says: > > Can't bind non-scalar value (currently) > > That tends to make one think an aref bind was attempted (at least it did for > me!). > > It might be more friendly to say: > Can't bind undef value > > and keep the other msg for aref bind attempts. > > Phil R Lawrence > prl ~AT~ cpan ~DOT~ org > >
