28.06.2014 12:47, Mark Rotteveel wrote: > But as a datapoint, PostgreSQL does this: > > "Read Committed is the default isolation level in PostgreSQL. When a > transaction uses this isolation level, a SELECT query (without a FOR > UPDATE/SHARE clause) sees only data committed before the query began; it > never sees either uncommitted data or changes committed during query > execution by concurrent transactions. In effect, a SELECT query sees a > *snapshot* of the database as of the instant the query begins to run.
Yes, I know. This is exactly what Nickolay offers. But PGSQL seems to have this since the very beginning, so they don't need to worry about backward compatibility and/or performance implications. Dmitry ------------------------------------------------------------------------------ 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
