On 07/24/14 21:27, Vlad Khorsun wrote:
- Original Message -
From: Mark Rotteveel m...@lawinegevaar.nl
To: For discussion among Firebird Developers
firebird-devel@lists.sourceforge.net
Sent: Thursday, July 24, 2014 7:35 PM
Subject: Re: [Firebird-devel] setCursorName in IResultSet
- Original Message -
From: Mark Rotteveel m...@lawinegevaar.nl
To: For discussion among Firebird Developers
firebird-devel@lists.sourceforge.net
Sent: Thursday, July 24, 2014 7:35 PM
Subject: Re: [Firebird-devel] setCursorName in IResultSet rather thanIStatement
On 23-7-2014 17:59
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 statement ?
As
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 statement ?
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,
@lists.sourceforge.net
Onderwerp: [Firebird-devel] setCursorName in IResultSet rather thanIStatement
Datum: vr, jul. 25, 2014 04:04
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
