Internal Website Search
1-37 of 37 resultsSchema Update The configuration element supports renaming packages, classes and fields in ObjectDB databases as a complementary operation to renaming or moving these elements in the IDE during source code ... when persistable classes are renamed or moved to another package. Running the application | |
Schema-Update: Rename superclass and remove one subclass Hello, we renamed a superclass and removed one of the subclass. If we then try to open ... public boolean onlyRecordLastStep = false; protected ChildClassB() { } } Then we rename SuperClass ... you for this report and for the test. It demonstrates well a bug in schema evolution that includes renaming | |
DB Explorer cannot be opened after schema package renaming of entity types The DB Explorer cannot be opened after schema package renaming of entity types because it seems that deprecated entity types which are removed from our java project break the database. In ... update tries to rename the package name for entity types and deprecated entity types | |
Schema evolution & renamed/moved enum Hello, I have an entity with an attribute of type enum say com.pkg1.MyEnum. I created a few instances of the class with this attribute of type com.pkg1.MyEnum and stored them in the database. Now, I moved that enum to a different package and renamed it say com.pkg2.MyNewEnum, which is not the new | |
Ambiguous entity name after package renaming I maintain an open source Java Swing application with 4 (ObjectDB) classes within 1 package. I renamed the package. And now I get a Ambiguous entity name PersistenceException error with reference to both the entity names (old and new) I now have 8 entities in de Explorer (4 old and 4 new). The new ones are empty. I tried to use schema update method: | |
Database Schema Evolution ). Any other conversion that is a valid casting operation in Java. Renaming (Package, Class and Field ... their names. When schema upgrade includes also renaming fields, classes or packages, these changes | |
Rename Application StringIdentityRename Application StringIdentity | |
ObjectDB Object Database Features automatically. Moving fields up and down in the class hierarchy is transparent. Support for renaming | |
Entity field renaming does not work Hello, we use the ObjectDB version 2.8.5_05. We want to rename a field in an entity and it does ... String comparisonDisplayDataTypeName; We added the schema for renaming to the objectdb config:   ... ; We have also class and package renaming for other entities and it works correctly. btc_es BTC | |
Schema-Update: Rename superclass and remove one subclass Hello, we renamed a superclass and removed one of the subclass. If we then try to open ... public boolean onlyRecordLastStep = false; protected ChildClassB() { } } Then we rename SuperClass ... you for your report. The test demonstrates a bug in schema evolution that includes renaming a super class | |
Schema update: package, class and field found in the manual only how a whole packet can be renamed : But Class3 shall not be moved. Or ... of moving a class and rename a field of the class doesn't works. I had extended a example in which i already rename a field. Only rename the field [example works]   | |
[ODB1] Chapter 9 - ObjectDB Explorer and rename directories and files. You can also use this dialog to create new directories and database files ... . You can also delete or rename a selected persistent class using the "Edit | Delete" and the "Edit | Rename " menu ... the database these objects are not affected. Renaming a class is useful as a complementary operation | |
Complex Schema Upgrade not working and Member). Our new hierarchy looks like that: - The package "member" has been renamed to package ... ; Only renaming packages worked well but when trying to make a schema upgrade with the classes results ... has been properly restarted. All other classes which just had package renames are working well. Any idea | |
Compare old and new schema of the entity classes but did not keep track of the changes. Some fields may have been renamed or removed, some classes may have been renamed or changed package. Is there a way for me to check what "format ... . It is feasible but difficult to keep track of all changes such as renaming attributes, renaming | |
Explorer in 2.3 to rename the Entity Classes (especially the package names). dmoshal David Moshal One further point: I'm ... described above. dmoshal David Moshal You can rename packages, classes and fields by using the configuration . This is preferred over renaming in the Explorer, because: Same changes | |
Automatic schema evolution causes ArrayOutOfBoundsException No fields or classes were renamed or moved to different packages. If I now want to read an Airline ... produce an unreadable database file. If I rename the permissions field to something else it works ... update without renaming the permissions field? Thanks for your help Markus Ritter doppelrittberger | |
Duplicate Entity class names causes Exception in Query content but renaming the classes are renamed e.g. Point - ODBPoint and ELPoint JFK John Francis | |
Primary key generation problem after changing entity package) Long id; } } Then I renamed A to B ... you test. First, with class A - so that instance of that class is added to database. Then, I renamed | |
Best practice: Database update/migration of embedded databases in products. Attributes added, removed and renamed . If attributes were removed, then only because the data ... - for renaming packages, classes and fields. The scenario in your post, of merging and splitting | |
@Transient persistance classes, e.g. adding/ renaming /deleting fields? wlboluyt Will Boluyt You are right | |
Database Files transaction. Trianglehead Json Error Don't expect a new file for every transaction, or renaming | |
ODB should auto-restart if it detects it's necessary into a class, then renaming it after a few minutes: com.objectdb.o._PersistenceException: Failed | |
Package name for persisted entities renaming classes by using the schema configuration . support Support | |
ODB lost? . Also notice, that a bug that was fixed in version 2.1.1_01 caused renaming the ObjectDB database file | |
Corrupted Database or error in ObjectDBExplorer? StimuliVectorImpl was renamed to VectorContainerImpl:   | |
The attribute column name (EXCEPTION) is a reserved SQL-99 keyword. but could be with other DBMS. To remove the warning, either rename your field (e.g. to exceptionText ), or add a Column | |
Massive schema update Hello, I need to rename /move a lot of classes in my project. I know how to do it with the configuration element, but it's a big database, and I guess that I am going to have a performance penalty, because ObjectDB is going to be translating old names to new ones all the time | |
Request clarification of changes to accessor enhancement policy (non-getter prefix instead of getter suffix) AND annotations; http://www.objectdb.com/object/db/database/version/2-6-5 - Renamed internal | |
exception thrown when try to run explorer again?-ee.jar i saw. I renamed objectdb-ee.jar to objectdb.jar This time i got this error: KadirBASOL:bin | |
objectdb:2.8.4 - Error occurred during initialization of boot layer directory and include only the objectdb-jee.jar file, which could be renamed to objectdb | |
ObjectDB 2.2.3 Added support of @ElementCollection (for setting eager fetch of non entity collections, such as List ). Improved performance of eager fetch in queries. Added Maven build enhancement to the bundled examples. Fixed a schema evolution bug in renaming user types. Fixed a bug in handling schema | |
ObjectDB 2.6.5 Added optional (experimental) support of using clients with different object model versions. Changed references to new flushed objects from ObjectDB to weak references. Cancelled an exception on cascading removal of an already removed object. Renamed internal Enhancer hidden methods to non | |
ObjectDB 2.8.6_08 Fixed field renaming schema upgrade of previous schema versions ( issue #2713 ). | |
ObjectDB 2.6.4 on EntityManagerFactory close. Fixed a bug in hierarchy schema upgrade. Fixed a bug in schema upgrade that includes both class and field renaming . | |
ObjectDB 2.9.3 Fixed unstable activation issues. Fixed issue #2954 - using IS NULL (or == null) on parameters in queries. Fixed automatic schema update on renaming or moving an enum type. Fixed issue #2964 (critical) - concurrent update of large objects with version-check=false. | |
ObjectDB 2.9.2_03 Fixed automatic schema update on renaming or moving an enum type. | |
ObjectDB 2.8.7 evolution ( issue #2726 ). Fixed field renaming schema upgrade of previous schema versions ( issue #2713 ). |