db4o Developer Community

Browse by Tags

• .NET
• C#
• Committe
• db4o
• Java
• Transaction Isolation
• Transparent Activation

• Committed callbacks, pushed updates and read committed isolation revisited

  Some time ago we presented Pushed Updates as a sample application for Committed Callbacks in this blog . Recently we put a similar mechanism in a slightly different context. Since we encountered some perceived ambiguity concerning db4o transaction semantics, Read More... Posted Wednesday, June 18, 2008 12:34 AM by Patrick Roemer | 1 Comments Filed under: Callbacks, Transaction Isolation

• Rollback strategies

  In this post Rodrigo introduced the concept of Transparent Persistence that makes developers life even easier as, once configured, db4o will take care of changed objects and make sure they are updated in the database (when the transaction gets committed) Read More... Posted Saturday, January 26, 2008 10:17 PM by Adriano Verona | 1 Comments Filed under: Java, .NET, C#, db4o, Callbacks, Transparent Activation Attachment(s): RollbackStrategySample.zip

• Committed Callbacks and Pushed Updates

  Committed callbacks have just been completed and checked in to SVN . You can now register a listener for the committed event and use it to keep all clients informed about changes committed by other clients. The syntax to register a committed listener Read More... Posted Monday, April 23, 2007 11:02 PM by Carl Rosenberger | 7 Comments Filed under: Callbacks, Committe