On 02/02/12 16:39, Adriano dos Santos Fernandes wrote: > On 02-02-2012 08:34, Alex Peshkoff wrote: > >> Looks like that when introducing cursors people wanted to follow some >> standard that existed that time. But from today POV this commands look >> useless and should better be removed - specially if they cause problems >> with engine stability. But probably somebody (Ann ?) knows why and what >> for were they introduced? It can be very useful to surely say 'remove >> them' or may be change our mind. >> > So if we remove it (and that enforces my opinion to do it), do you think > it's important to maintain Statement::insert only to make > isc_dsql_insert work with old servers? > > Or could we remove Statement::insert (but then isc_dsql_insert should > return error directly in the client)?
I think that if isc_dsql_insert() is needed for people on old servers that means that BLOB SQL commands are still in use and should not be removed from FB3. I.e. if we remove cursor BLOB support, Statement::insertis also not needed and should be removed. And yes - isc_dsql_insert() will return error directly on client. ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
