15.10.2010 17:57, Alex Peshkoff wrote:

> On 10/15/10 19:09, Dimitry Sibiryakov wrote:
>> 15.10.2010 16:59, Alex Peshkoff wrote:
>>> What we started to discuss is 'Is the fact that isc_dsql_execute()
>>> agrees to work with EXECUTE PROCEDURE a bug or documented behavior?'
>> And everybody except Jim agreed that this is a bug.
> Documented bug becomes feature :-)

Bug in documentation shouldn't be considered as a specification for development. ;-)

>> Jim insists that this was original design. If Jim is right, first fetch from EXECUTE
>> PROCEDURE must return data and subsequent ones - 100.
> I think that the fact that it does not return 100 is a bug.

Agree.

>> However, in this case one question left: what if the procedure is selectable (i.e. uses
>> SUSPEND)? Shouldn't in this case all records be fetched before end-of-data and EXECUTE
>> PROCEDURE to be effectively the same as SELECT?
> No.

Why not? It would bring our syntax a bit closer to MS SQL without loosing standard
conformation.

--
SY, SD.