On 10/18/10 12:13, Dimitry Sibiryakov wrote:

> 18.10.2010 9:21, Alex Peshkoff wrote:
>> EXECUTE PROCEDURE is parsed as special kind of SQL operator, which (if
>> user thinks about roundtrips) must be executed with special API call.
>> Imagine that call used in a case when multiple rows should be returned.
>> May be it's possible to fetch more rows from such statement, but how can
>> used know, should he do it or not? Moreover, to get an idea about it,
>> statement start to execute. All together all this looks far not good for me.
> AFAIK, this "special API call" can be used for executing of SELECT too. If used without
> output SQLDA it requires SELECT to be singleton (and must start to execute it to know
> whether it is). Without output SQLDA, it allows one or more fetch calls to retrieve result
> set later. So, what's the difference?

If I use it with output SQLDA, I will have to each time check - may be
there some more data to fetch? This destroyes the whole idea of
minimizing roundtrips.