Thank you for setting me straight. As chance would have it, I also had
another set of eyes look at it here and come up with the same
thing... actually, now that I think of it, I did come to this conclusion a
couple of other times but kept forgetting it.
Basically, if I did $outObj->param("\"NULL\"") then I would've got the
string NULL that I was thinking should've been passed. I don't know why I
didn't recognize this earlier when I was printing $cmd and viewing the
$outObj object in the debugger. I guess it's just been one of those days
that I should've stayed home and slept.
Thanks again Michael.
On Thu, 3 May 2001, Michael Peppler wrote:
> Curt Russell Crandall writes:
> >
> > Now, what has me scratching my head is why when I define an input argument
> > to this stored proc as "NULL" the string, it is showing up in the database
> > as [NULL]... this is what I want, but I'm wondering why it is working... I
> > would think that the database would've interpreted it as the string NULL.
>
> It's fairly straightforward, once you look at what you really pass to
> the stored proc.
>
> If you pass NULL (unquoted) then Sybase will store a NULL value.
> If you pass 'NULL' or "NULL", then Sybase will store the NULL string.
>
> So to really find out what is happening, print out the $cmd string.
>
> Michael
> --
> Michael Peppler - Data Migrations Inc. - [EMAIL PROTECTED]
> http://www.mbay.net/~mpeppler - [EMAIL PROTECTED]
> International Sybase User Group - http://www.isug.com
> Sybase on Linux mailing list: [EMAIL PROTECTED]
>
