ObjectDB Database Search
101-110 of 110 resultsWorking with a cleared cache event callbacks. ObjectDB should produce better error messages, but if the same code works outside | |
How to apply constraints in collection attributes of entity. JDO's Unique annotation . For other constraints you can check objects in lifecycle events . support | |
Master database switching to read-only mode, possibly caused by slave failure of events was: 13:20 - our monitoring reported GC time per minute on the SLAVE instance over 30 | |
Merge of entity classes with "mapped by" very slow - one with mapped by, second with adding entities list without "mapped by". The difference is huge event | |
_UserException: Attempt to open a database file '...' that is currently in use I have an application which runs correctly in NetbeansIDE but after building it, it won't just run sometime, the app stop responding to event at a particular point. I was able to reproduce this issue while running the jar file in command line and I got this exception which I have it stack attached | |
Problems Running ODB Explorer(Timer.java:244) at java.awt. event .InvocationEvent.dispatch(InvocationEvent.java:251) at java.awt | |
Error when using Object DB Java Agent(SAXParserImpl.java:333) at ch.qos.logback.core.joran. event .SaxEventRecorder.recordEvents(SaxEventRecorder.java | |
Deadlock, if two threads try to close an entity manager Hello, we get into a deadlock, if two threads try to close an entity manager. The first thread try to close the entity manager factory which close all opened entity managers. The second thread is triggered by an event and try to close the entity manager after a database access. Both threads | |
Problems down-casting in WHERE clause is also thrown for the following simpler query: SELECT e FROM Event e WHERE TYPE(e) = Practice AND ((Practice | |
ObjectDB 2.9.5_02 Enhanced security by disabling Java methods in queries . Updated the default objectdb.conf file. Delayed @PostUpdate events to include all transaction changes. Fixed a bug in using java.time.Instant . Fixed a bug when using more than 2147483648 entities of the same class in a database ( issue #3044 ). |