db4o Developer Community

Hi Maik, The test case I provided works well in embedded mode, but in a c/s configuration the exceptions are thrown. I filed the bug under http://tracker.db4o.com/browse/COR-767.  Cheers, Andreas 

I supplied a patch in jira. (http://tracker.db4o.com/browse/COR-738). This patch adds a new Message for just closing the socket without terminating the current transaction. I hope this is the correct handling for blobs.   - Andreas 

Hello *, when switching the database file in c/s mode and using a blob read or write operation, the BlobProcessor closes the current transaction (Is this how it should be???), but db4o continues to use this open transaction. So closing the ObjectContainer results in a NullPointerException, because the Server couldn't find the correct ...

Another idea: Seperate the reference cache from the transaction from the client. Right now, a user has to get an object again for each transaction/client. In a server application where many clients are operating many concurrent transactions, it would be much better if the server maintained a single connection to the DB and a single reference ...