| Subject | Re: [ib-support] SELECT in stored proc returns wrong value |
|---|---|
| Author | Paul Reeves |
| Post date | 2001-06-18T05:03:09Z |
Christian Gütter wrote:
not see nulls returned. Nothing is returned. If you see nulls on the client side
this will be due to some massaging on the part of your client side middleware.
It will have prepared an XSQLDA to store the row. If nothing comes back the
client may interprete the results as NULLS.
In your stored procedure you have uninitialized variables. The query returns
nothing. The variables remain unchanged. This time there is no client to
interprete anything - just the next line of your code.
Paul
--
Paul Reeves
http://www.ibphoenix.com
taking InterBase further
>Yes. When you execute a dsql statement that doesn't return a result set you will
> For me, this is not consistent behaviour.
> So one might call it a bug, not a serious one, but still a bug.
>
> Any objections?
>
not see nulls returned. Nothing is returned. If you see nulls on the client side
this will be due to some massaging on the part of your client side middleware.
It will have prepared an XSQLDA to store the row. If nothing comes back the
client may interprete the results as NULLS.
In your stored procedure you have uninitialized variables. The query returns
nothing. The variables remain unchanged. This time there is no client to
interprete anything - just the next line of your code.
Paul
--
Paul Reeves
http://www.ibphoenix.com
taking InterBase further