Carl Karsten wrote: > > So other connections don't see the updates (INSERT, UPDATE, DELETE) until the > commit? > > I was under the impression that once a transaction was started, a SELECT on > "that data" would wait till the transaction was done so that the SELECT would > return 'current' data, where current includes changes made after the > transaction > started. > > Maybe lock is the wrong term. blocking? > > Carl K
For a start read here: http://en.wikipedia.org/wiki/ACID There a quite different architectures to maintain the rules for ACID. One of them is locking which is common in "desktop databases", a more modern way is the "Multi Generational Architecture". It either cases it depends on the selected isolation level. http://en.wikipedia.org/wiki/Isolation_%28database_systems%29 Uwe _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
