On 24-7-2014 12:30, Alex Peshkoff wrote: > That move was not directly related with TCS fail. Originally setting > cursor name remained in effect only for cursor life-time - i.e. after > isc_dsql_free_statement with DSQL_close option cursor name was > destroyed. If we set cursor name for statement, semantically it should > exist after closing cursor. But this breaks applications (starting with > IBO components) that tend to set new cursor name for each statement > execution.
How did it break these applications? Setting a different cursor name should be allowed if there is no cursor open (especially if you look at the SQL CLI standard). > But what solution can we suggest? Move setCursorName back to IStatement > and blank it when cursor is closed? Last is required to make IBO happy. > IMHO in old API this is required. But what about new one? What it worse > - change in behavior or ugly semantics? A cursor name should remain set for the lifetime of the statement, unless it is explicitly set to a different value. 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
