On Mon, Sep 24, 2001 at 08:11:12AM -0600, Sterin, Ilya wrote:
> Ronald, but (not necessarily in this case, since it's a count(*) query), but
> for most others it will also return the first column selected and set it to
> undef if that column is NULL, so therefore it will also call the dbError()
> sub. The difference with this, is the count(*) returns something, (0+) all
> the time, so this won't be a problem, though in general this is not a very
> good practice. RaiseError and eval are the best solutions:-)
Yup, you make a good point. RaiseError/eval and checking the result of the
execute are better, more general solutions.
I should have caught up on all the list mail before replying. :)
Ronald
