Db4o officially stops supporting and object-oriented databases.

Db4o officially stops supporting and object-oriented databases.

I tried db4o some time ago. I really felt good, But I searched for it in China and did not find any special forum or object-oriented database products, I am deeply aware that this is not very popular in China. But I think this is really good (of course, it also has its own strengths and weaknesses), so I have established this website to promote it (object-oriented database communication community ).

However, when opening db4o's official website today, we found that Versant no longer supports db4o. This makes me very sad...

In any aspect, this is definitely a very sad decision. I personally think that db4o is the best object-oriented database, the official charging object-oriented database system gave up db4o, probably because of economic considerations.

However, I hope the official team can transfer this excellent database to the community for further development, or is there anyone interested in continuing development based on db4o. It is a pity that I can use a database myself. Developing a database is really not good. If I can, I want to do this database myself as a product in this community.

Of course, a better idea is to develop a branch product for db4o so that everyone can continue to enjoy and improve db4o. If someone can continue to write a branch for db4o, I am willing to do my best to help.

Although the official website does not support it, the official website has provided us with a very good object-oriented database. I will continue to write for this database, answer questions, and provide some downloads. These will be carried out in the object-oriented database exchange community on my website. If you are interested in the database and want to settle on my website, there may be less popularity in things and so on, but I believe it will be better and better under my own business.

Write so much. I will continue to support the development and promotion of object-oriented databases in China. I believe I will do better. Then, I am really looking for friends who are also interested in object-oriented databases to run this website with me.
Some bugs of DB4O in the object database and how to deal with them

2. objectmanager 6.0 needs to correspond to the version of db4o 6.1. objectmanager 1.8 needs to correspond to the version of db4o 5.5. If objectmanager 1.7 does not correspond to the version of db4o 5.2, the database file cannot be opened, why is it so incompatible? Even higher version management tools cannot open old databases. 3. com. db4o. eclipse_0.2.0 can only open databases of db4o 5.2 by default. You can modify the com. db4o. eclipse. db4o in the plugin_0.2.0.jar package. change the jar file to a different version and then access the database of the corresponding version. Decompress com. db4o. eclipse. plugin_0.2.0.jar package to com. db4o. eclipse. plugin_0.2.0 directory method one: The db4o-5.5-java1.2.jar or db4o-6.1-java1.2.jar jar files renamed to db4o-5.0-java1.2.jar, and then copy to overwrite the original db4o-5.0-java1.2.jar file, re open Eclipse can be. Method 2: Copy jar files such as db4o-5.5-java1.2.jar or db4o-6.1-java1.2.jar to com. db4o. eclipse. under the plugin_0.2.0 directory, and then enter com. db4o. eclipse. under the plugin_0.2.0META-INF directory, open MANIFEST. MF file, replace the db4o-5.0-java1.2.jar inside with the corresponding version of the jar file name, save, re-open Eclipse. The two methods are actually replacing different versions of jar files. 4. If there is a problem when you use a tool to open it, you also need to go to the current user's directory and delete files such as. objectmanager. *, and then run the tool to open the database.

Some bugs of DB4O in the object database and how to deal with them

2. objectmanager 6.0 must correspond to db4o 6.1.
Objectmanager 1.8 must correspond to the version of db4o 5.5.
Objectmanager 1.7 must correspond to the version of db4o 5.2.
3. com. db4o. eclipse_0.2.0 can only open databases of db4o 5.2 by default.
You can modify the db4o. jar file in the com. db4o. eclipse. plugin_0.2.0.jar package and change it to a different version to access the database of the corresponding version.
Decompress com. db4o. eclipse. plugin_0.2.0.jar package to com. db4o. eclipse. plugin_0.2.0 directory method one: The db4o-5.5-java1.2.jar or db4o-6.1-java1.2.jar jar files renamed to db4o-5.0-java1.2.jar, and then copy to overwrite the original db4o-5.0-java1.2.jar file, re open Eclipse can be.
Method 2: Copy jar files such as db4o-5.5-java1.2.jar or db4o-6.1-java1.2.jar to the com. db4o. eclipse. plugin_0.2.0 directory,
Then enter com. db4o. eclipse. plugin_0.2.0/META-INF directory, open MANIFEST. MF file, replace the db4o-5.0-java1.2.jar inside with the corresponding version of the jar file name, save, re-open Eclipse.
The two methods are actually replacing different versions of jar files.
4. If there is a problem when you use a tool to open it, you also need to go to the current user's directory and delete files such as. objectmanager. *, and then run the tool to open the database.