db4o Transparent Persistence

So after much haggling of code, testing and pointless circumspection.
I’ve come to realise db4o by default, does not allow for Transparent Persistence of object modification across threads or instances.
So even if  you .store() or .commit(), you will end up with a possible ill-formed object or inconsistent data object.

So after much searching and peering into the nature of the beast, to solve this problem you need to turn on TP (Transparent Persistence).
Unfortunately, it’s a ant build script…….so exciting…..anyways, here’s the link: TP

Don't be shellfish...Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedInShare on TumblrEmail this to someone

Leave a Reply