57 | Removing entity class the 10 entities limit and got exception: com.objectdb.o.UserException: Too many persistable types (>10) - exceeds evaluation limit Among the 10 entities in the project there are 2 entities I added long ... , but there are still in ObjectDB database. The 2 tables for these entities are empty, but the tables exist, so they count |
57 | DB Explorer cannot be opened after schema package renaming of entity typesThe 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 the database the entity types and deprecated entity types can be part of the identical package. The schema |
11 | References to objects of missing obsolete entity classes: When we migrate our product profiles, we get an exception regarding entities that were removed in an earlier version of our product (see below). These entities are not present in the database and the error does ... a dummy (enhanced) entity class in your project for that obsolete entity class. support Support |
11 | New entity objects are duplicated on merge cascadingWhen merge is cascaded to a new entity object that has not been persisted ... .persistence.*; @Entity public class T595 { public static void main(String[] args ... (); } @Entity public static class Book { @Id @GeneratedValue(strategy |
11 | Unexpected exception during query, if entity is not enhancedHello, the entity TCVector is not enhanced and the enhancement check in the objectdb.conf is active ... again. This could happen, for example, if that class is a subclass of another entity class that was changed (e.g. a field was added) after that enhancement. Rebuilding and re-enhancing of all the entity |
11 | Auto Generated Values for entity objects with no primary key fields defined (as explained in the previous section). The same ... @GeneratedValue with the AUTO strategy: @Entity public class EntityWithAutoId1 { @Id @GeneratedValue ... definition is equivalent: @Entity public class EntityWithAutoId2 { @Id @GeneratedValue long |
11 | JPA Named Queries is attached to exactly one entity class or mapped superclass - usually to the most relevant entity ... carefully to avoid collision (e.g. by using the unique entity name as a prefix). It makes sense to add the above @NamedQuery to the Country entity class: @Entity @NamedQuery(name="Country.findAll |
11 | DELETE Queries in JPA/JPQLAs explained in chapter 2, entity objects can be deleted from the database by: Retrieving the entity objects into an EntityManager. Removing these objects from the EntityManager within an active ... an alternative way for deleting entity objects. Unlike SELECT queries, which are used to retrieve data from |
11 | ObjectDB Object Database Features). Up to 2,147,483,648 entity classes per database file. Up to 2,147,483,648 indices per database file. Up to 9,223,372,036,854,775,808 entity objects per database file. Unlimited database connections (limited ... connections and timeout. Caching L1 entity object cache (per EntityManager). L2 shared entity data |
11 | Unexpected error when loading all entity instanceHi, when going through all entity instance to find orphaned entries we get the exception ... . Create a transaction and load 10.000 entity instances 2. Check for each entity instance ... remaining was 5GB so there is also no issue. I checked my logs and found the error: Entity is not |
