Andrew Zhang - 23/Jun/07 01:35 AM It's read only now in IoAdapter layer. But some callers still try to write things into a read-only databas. Has to be fixed soon. It also makes cc failed.

Neeraj Joshi - 18/Jul/07 11:27 AM We have seen following behaviour: 1) Readonly mode is On. Objects are saved into the database. Querying the database returns 0 result count. Objectmanager does not show any stored classes. However, shows only size of db that make us feel that objects are there in the database. 2) Readonly mode is Off. Objects are saved into the database. Querying the database returns proper result count. Now switching the Readonly mode to On. Adding few more objects to the same database. Querying the database returns only those objects which are saved when the Readonly mode was Off.

Andrew Zhang - 18/Jul/07 12:23 PM Hi Neeraj, which version did you use? 6.1 or 6.3? Objects can not be stored into the database if readonly mode is on. In 6.3, db4o throws an exception for such case. Could you please describe your environment? Thanks!

Neeraj Joshi - 18/Jul/07 12:43 PM This simple testcase shows the behaviour in a comment. Please suggest if i do anything wrong.

Andrew Zhang - 18/Jul/07 01:44 PM Hi Neeraj, Object can not be stored if db4o is configured as read-only. db4o 6.1 returns silently, and the behaviour has been changed in version 6.3. Would you please take a try with version 6.3? Thanks!

Neeraj Joshi - 23/Jul/07 07:33 AM Thanks Andrew for your suggestion. I am using 6.1 version earlier. Now I have tried the test case with latest 6.3 and it seems there that you cannot add new objects into the readonly database. An attempt to do that is throwing an exception for the same. It looks now the bug is fixed.