On 06/25/14 10:49, Roman Simakov wrote: > Hi, all! > > My 2 cents. Current behavior is really a BUG and I cannot imagine who > wants to have such logically incorrect data.
A sample. Warehouse has a number of workplaces with computers for shipping goods. At some workplace in the beginning of a day were shipped some antennas, books and computers. I.e. we are at the top of the grid, cursor is opened but not fetched to the end. Next client wants some umbrellas and asks how much is present now. Grid is scrolled up to umbrellas - and please answer what quantity of them do we prefer to see - current or present at the beginning of a day? > It's enough for me to > make a conclusion to have new behavior as default. Some developers who > really understand that such situation cannot happen in his system can > EXPLICITLY specify TPB option isc_tpb_insensitive_cursor. I assume > current applications relies on logically correct result so backward > compatibility will not be broken. > They also rely on the fact that RO RC transaction does not prevent GC... And when one is using RC transaction he must be ready to get not consistent data in it. ------------------------------------------------------------------------------ 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
