Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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 ?
Some features do not work:
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.