87 | Schema Update large refactoring to do an automatic schema update of our database using the objectdb.conf file. The old package structure looks like ... , if it is possible to perform some sort of wildcard schema update, instead of specifying all the thousands ... to perform some sort of wildcard schema update Wildcards are not supported. > will there be any limit |
87 | Schema-Update: Rename superclass and remove one subclass to RenamedSuperClass and Remove the ChildClassB. <schema> <package name="schemaupdate.delete"> <class name="SuperClass" new-name="RenamedSuperClass" /> </package> </schema ... and for the test. It demonstrates well a bug in schema evolution that includes renaming a super |
85 | Activation error on Schema change, and actually any change to your schema may cause a similar exception. Please verify ... . Even when objectdb.conf with old license key where copied to new version directory. No schema change |
85 | Schema Update: class hierarchy changeHello, we try to change the class hierarchy of an Entity. You wrote www.objectdb.com/database/forum/899 that ObjectDB support automatic schema evolution for adding and removing fields and for class ... up and down in the class hierarchy as part of the automatic schema evolution |
85 | Indexes broken after schema update.Anyone else noticed this? I updated an entity Object with some new fields, restarted the database to pick up the new schema and now none of the indexes work, except the @Id. I can query by any field ... before using the revised schema. It is a common operation to add persistent fields to existing |
85 | Schema evolution & renamed/moved enum to use the <schema> tag in the config file because my enum is not an entity. What is a the proper way ... automatic schema evolution is currently not supported. If you have to update a field type into a non |
17 | Feature Request: Subclassed PersistenceException for Type Not Found in DB Schema with different schemas managed by the same ObjectDB server that are sharded based on the day. We let ObjectdDB create the schema in each ODB file the first time objects are persisted. The problem is that when a process runs that querys a shard before the schema is created a generic PersistenceException |
17 | Collision Between Different Schema Versions of Entity ClassesVersion 2.8.4 fixes a critical bug that in rare cases may cause collision between different schema versions of entity classes, when schemas have changes many times (usually more than 20 times). This bug mainly affects queries on hierarchy of multiple entity classes (i.e. a query on a super class |
17 | Compare two schemas or odb filesFor example, if we make a backup of our database it would be helpful to have the possibility to compare the backup schema (odb file) with the current version in the database and as result we should get the difference between the two schemas. It would also be sufficient, if we can compare object |
17 | Crash after altering schemaHi, I got an exception after altering Schema.... (just adding an index). --- bmpccdeMac-mini:CloudAI eko$ java -jar build/libs/asli-cloudai.jar Current Working directory /Users/eko/work/asli ... (Thread.java:832) eko EKO FAJAR Note that after schema change you have to restart the server |
