About schema

forum_thread

significant performance decrease

we are using objected in embedded mode (on OS X and WINDOWS). The database increased now to around 400000 entities of one class (database file size around 1.5 GByte). The response time of standard queries increased with this database size to an unacceptable rate (several seconds compared to around 30% when the number of entities was just half of the current). We tried to optimize the cache settings, current objectdb.conf is: <!-- ObjectDB Configuration --> <objectdb> ... "false" /> </entities >   <schema > </schema >   <server > <connection port = ...

 
release

2.3.3

... to the bundled examples. Fixed a schema evolution bug in renaming user types. Fixed a bug in handling schema evolution (regression of 2.2.0). Fixed a bug in ...

 
release

2.2.1

... issue #36 ). Fixed a critical bug in schema evolution of modified ancestor classes. Fixed a bug in ... proxy objects with ordinary objects. Fixed a schema evolution bug when adding a new super entity class . ...

 
issue

InternalException

Hi, 3 Days before our rollout.. We've just got this when trying to commit persist of a bunch of entities into the DB   ... Have you changed the schema recently (e.g. added new persistent fields)? Do you still get ... The exception may be the result of changing schema without restarting the database. ObjectDB ...

 
forum_thread

The server cannot start in CentOS

Hi, I try to run ObjectDB from Linux, but failed. My command is: java -cp objectdb.jar com.objectdb.Server start The result is attached. After typing the command, the system seems halting. ... exception that you got might indicate an internal ObjectDB schema validation problem. ObjectDB Support ... "false" /> </entities >   <schema > </schema >   <server > ...

 
release

2.2.0

... issue #36 ). Fixed a critical bug in schema evolution of modified ancestor classes. Fixed a bug in ... proxy objects with ordinary objects. Fixed a schema evolution bug when adding a new super entity class . ...

 
forum_thread

Replication error on slave restart

I'm trying to enable replication on master server that was running with "recovery" enabled previously. I have copied database file to slave... and so on by manual. It worked fine. But if I restart slave server: ... = "false" /> </entities > <schema > </schema > <server > <connection port = "6136" ...

 
release

2.3.2

... to the bundled examples. Fixed a schema evolution bug in renaming user types. Fixed a bug in handling schema evolution (regression of 2.2.0). Fixed a bug in ...

 
forum_thread

Package name for persisted entities

Hi, I have a question about package name and searching for entities. As for now we were using two different databases for two different parts of our system. But we want to make a 'common' model for both systems. After merging entities from two different projects, we get single jar with all entities. Unfortunately some of the names are the same for entities: - homplex.model.dbobject.Inspiration - pl.hplxtool.model.Inspiration ... Finally, consider renaming classes by using the schema configuration . ObjectDB Support ObjectDB ...

 
release

2.3.1

... to the bundled examples. Fixed a schema evolution bug in renaming user types. Fixed a bug in handling schema evolution (regression of 2.2.0). Fixed a bug in ...