61 | Entity can be found by find() but not by query(), with a query it is not always possible to get the entity, sometimes we get the entity ... until it commits on a separate snapshot of the database that includes its own updates but not updates ... , although such an issue is not expected. You may try disabling the query cache to see if it helps. As |
61 | ObjectDB size not reducing and the size does not decrease. In fact it keeps growing as records decrease. Is that supposed to happen? FYI: The DB is client server mode, and it is not being restarted as records reduce, as it is live in production. I do an hourly backup and the backup file is not any smaller(it gets bigger) each hour as |
61 | Type ... is not defined as an entity (@Entity is missing) (error 302).epimss.lab.data.bacti.CultureRqst is not defined as an entity (@Entity is missing) (error 302) at com ... RequestDateAndNumber() } // end class Culture I am using JDO, NOT JPA. Thanks for any help. st ... to its own JDO API by packaging. Hence if I use another JDO jar other problems arise. I am not sure how I |
61 | Annotations not supported in -source1.3 (use -source 5 or higher ..) and other files: Annotations not supported in -source1.3 (use -source 5 or higher ..) Generics not ... see that this could explain the error) I could not figure out how to fix this in the points project in Netbeans, I did not find a setting for the Java version there, so I created a fresh basic Java Application in |
60 | Entity Type is not found (error 301) in Query User is not found (error 301) (position 14) at com.objectdb.jpa.JpaQuery.getResultList(JpaQuery.java ... This could happen if the entity class is not in the database yet (no instances of that class have been persisted yet), and a persistence unit is not defined. If this seems to be the cause, either define |
60 | @Column length is not working. with a string that has more than 16 character, not able to get any error or exception from ObjectDB. It should give an error for exceeding the limit. But dose not throwing any error or exception ... then it is not that expensive. You can use external validation libraries, but they will not be faster. support Support |
60 | package not found running ObjectDB under OSGi datamodel.core.base is not found by the enhancer (error 108) The Enhancer was run in the following way ... you have a bug ?? Thanks in advance b Tomasz Tomasz Wozniak This is not a bug but a limitation. Java doesn't ... of specific file based class loaders (by scanning the file system) but not in the general case |
60 | java.sql.Date equals comparison not working with CriteriaAPI why this might be the case? Note: We can currently not update the ODB version as this is a production system. Note ... a new build. However, since you will not be able to use a new build, try as a workaround to replace ... is irrelevant. As can seen above in the query's toString (not shown in version 2.4.5), the date literal |
60 | BTree 8 is not found at com.objectdb.o.JPE.d(JPE.java:91)._RollbackException: Failed to commit transaction: Unexpected database state: BTree 8 is not found at com ... .AuDatabase.transact(database.kt:64) at server.test.ChangeListenerTest.Should not publish same object ... is not found at com.objectdb.o._PersistenceException.a(_PersistenceException.java:47) at com |
12 | Enhancement does not show an error message when an outdated license is used. The entities were not enhanced in our jars. But the message from the enhancement tool com.objectdb.Enhancer ... _es BTC EmbeddedSystems Thank you for this report. Enhancement does not require a valid licence (e.g ... ). However, if there is no valid OEM activation then although the classes are still enhanced and usable they are not signed |
