Search code examples
configurationdb4o

What are the main issues with a db4o server without the persistent classes available?

I was told in a previous question that there can be issues when using db4o server without persistent classes. On the Versant web site, they just say that native queries won't be available.

So what are the issues possible in this particular configuration, except less features ?

Solution

  • Some features do not work:

    • All query methods except SODA queries do not work.
    • Some type of objects my create issues like enums etc.

    The main concern is just the 'stability' and 'matureness' of this feature. db4o hasn't been design to work without the classes available. The test-suite and feature design is centered around scenarios with classes available.

    Or from the internal implementation standpoint: The 'generic'-reflection layer is very brittle. That's the component which is required for this feature.

    Well if up for taking a risk and only use SODA as query engine you can try it. However if you rather do not run into bugs / limitations than avoid it.