On 07/24/14 21:27, Vlad Khorsun wrote:
> - Original Message -
> From: "Mark Rotteveel"
> To: "For discussion among Firebird Developers"
>
> Sent: Thursday, July 24, 2014 7:35 PM
> Subject: Re: [Firebird-devel] setCursorName in IResultSet rather
&
I was talking about statement level result sets (cursors) not connection or
engine level, so I'd say that what I was saying is not "utter nonsense".
Mark
- Reply message -
Van: "Jim Starkey"
Aan: "For discussion among Firebird Developers"
Onderwerp
That is utter nonsense. If there weren't a possibility of multiple active
statements, there would be no need for naming statements,
This flies in the face of the Interbase/Firebird architecture that support an
arbitrary set of active/open statements from the datpy it was born.
> On Jul 24,
On 24-7-2014 19:27, Vlad Khorsun wrote:
>> As far as I understand it, you can't have an IResultSet unless the
>> result set is open, so setting the cursor name on an IResultSet is not
>> very logical.
>
> What about more than one simultaneously active result set produced by
> the same stateme
On 24-7-2014 19:27, Vlad Khorsun wrote:
>> As far as I understand it, you can't have an IResultSet unless the
>> result set is open, so setting the cursor name on an IResultSet is not
>> very logical.
>
> What about more than one simultaneously active result set produced by
> the same stateme
- Original Message -
From: "Mark Rotteveel"
To: "For discussion among Firebird Developers"
Sent: Thursday, July 24, 2014 7:35 PM
Subject: Re: [Firebird-devel] setCursorName in IResultSet rather thanIStatement
> On 23-7-2014 17:59, Adriano dos Santos
