Hi, At June 24, 2014, 12:45 PM, Dmitry Yemanov wrote:
> 24.06.2014 17:35, Daniel Rail wrote: >> >> I don't think it takes out the non-blocking behavior, because the >> blocking is only performed at the statement level, not the transaction >> level. So, for a lookup dataset, it would not change a thing, since >> the query results will always pick up committed data everytime it is >> executed, within a READ COMMITTED transaction. > I'd say the problem is more about data grids (that can stay open -- but > not fully fetched -- for a long time) than about lookup controls. That would be one scenario that can be problematic. So, I think it would be to add another transaction isolation level: READ COMMITTED SNAPSHOT. That would guarantee that the data is consistent while the query is being executed and while the cursor is open, but still remaining a non-repeatable read transaction. And, the READ COMMITTED isolation level can stay as it is today. -- Best regards, Daniel Rail Senior Software Developer ACCRA Solutions Inc. (www.accra.ca) ACCRA Med Software Inc. (www.filopto.com) ------------------------------------------------------------------------------ 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
