On 28-6-2014 09:49, Dmitry Yemanov wrote: > 28.06.2014 11:01, Mark Rotteveel wrote: >> >> If a cursor is open, and the SQL-transaction in which the cursor was >> opened makes a significant change to SQL-data > > At the first glance, this is what we called "cursor stability" and have > fixed in FB3. But in fact it covers other cases as well and I don't > think we support them (e.g. DSQL cursor is open, one row is fetched, > then an update is posted, then the second row is fetched).
As far as I understood, the cursor stability fix was about changes made by the statement to its own data (eg an UPDATE or DELETE). The text I quoted defines significant changes as "if and only if it is independent of CR, and, had it been committed before CR was opened, would have caused the sequence of rows in the result set descriptor of CR to be different in any respect" Mark -- Mark Rotteveel ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
