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, 2014, at 4:04 PM, Mark Rotteveel <[email protected]> wrote: > > 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 far as I know Firebird still doesn't support multiple result sets, > and most implementations I know with multiple result sets either require > or allow only one result set open at a time (and if they allow multiple > result sets open, that is usually achieved by fully reading and > detaching previous result sets). > > Mark > -- > Mark Rotteveel > > ------------------------------------------------------------------------------ > Want fast and easy access to all the code in your enterprise? Index and > search up to 200,000 lines of code with a free copy of Black Duck > Code Sight - the same software that powers the world's largest code > search on Ohloh, the Black Duck Open Hub! Try it now. > http://p.sf.net/sfu/bds > Firebird-Devel mailing list, web interface at > https://lists.sourceforge.net/lists/listinfo/firebird-devel ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
