Re: Re: Calling a Sybase Procedure with NUL in a parm

to answer your question, the parameter is indeed a VARCHAR field. Hadn't thought about converting to hex...though something tells me that the application on the other side won't like it. Worth a shot though...++ for you!

thor

Comment on Re: Re: Calling a Sybase Procedure with NUL in a parm

Replies are listed 'Best First'.
Re: Re: Re: Calling a Sybase Procedure with NUL in a parm by mpeppler (Vicar) on Feb 05, 2003 at 16:30 UTC
May I ask why you need to store a packed value in a varchar column? Wouldn't binary/varbinary be more appropriate? Now having said that this might still be a bug with DBD::Sybase - I'll look into it. Michael	[reply]
Re: Re: Re: Re: Calling a Sybase Procedure with NUL in a parm by thor (Priest) on Feb 05, 2003 at 23:24 UTC
You're asking exactly the question that I asked. However, this table has existed for 10+ years with the behavior that I've described. Basically, we have a process that communicates with other processes bi-directionally though this table. The column in question is the "message type". Why it wasn't stored just as a straight up integer is beyond me, but like I said, I've been handed a steaming pile and I have to deal with it. thor	[reply]