|Subject||Re: [IBO] Using Stored procedures exclusively|
> I presume Jason is saying that he will add the capability of IBOrecognizing
> primary key return values if so coded. that's slick and would be useful.Thank the people who (I'm presuming) fixed the bug so that it is possible to
> thanks Jason! We'll definitely check it out when its ready.
do this now.
Before, it got the internal XSQLVAR message parameters mixed up and returned
error messages if it wasn't prepared each time.
Now it can be prepared, do a singleton operation and return values all in
one shot and remain prepared.
> re: interactive queries we'vbe been using SQL like this that works:SELECT
> * FROM my_procedure WHERE myField=1 and it seems to work just fine. Ihave
> not yet verified that the result set limits are applied on the server thenits
> sent versus applied on the client but I'm guessing its done on the server,
> so I am not sure why the interactive query stuff won't work. Obviously
> something we haven't been using yet.This is not recommended unless the result sets are VERY small and you are
doing minor refinements.
The stored procedure cannot optimize query criteria in the WHERE clause of a
CPS - Mesa AZ