On Fri, 25 Jul 2014 12:49:37 +0400, Alex Peshkoff <[email protected]> wrote: > On 07/25/14 03:23, Adriano dos Santos Fernandes wrote: >> Em 24-07-2014 17:30, Vlad Khorsun escreveu: >> >>> So, currently we really have no way to call >>> IStatement::openCursor... >>> >> BTW, isn't openCursor a bad name too, since it actually executes (not >> only "open") the query, and it returns a IResultSet (not ICursor)? >> >> I prefer the JDBC name, as our API is based on it at some level: >> executeQuery. > > Currently there are 2 methods for statement execution - openCursor(used > for SELECT) and execute(used in other cases). Changing first to > executeQuery and leaving second as is looks far not good. So please > suggest new pair of names.
For reference: JDBC uses executeQuery (which produces a ResultSet), executeUpdate (for queries that do not produce a ResultSet), and execute (for queries where you don't know if they produce result set, or if they produce multiple result sets). Mark ------------------------------------------------------------------------------ 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
