ObjectDB Database Search
51-68 of 68 resultsIs 2 level cache in use? Hi, Is there any way to check, if 2 level cache is in use? Right now I've done two things: 1. objectdb.conf with cache size is placed in WEB-INF directory of my web application. 2. persistence.xml was modified with: But after few benchmarks I don't really see any difference in performance. ODB | |
Problem with distinct select, order by and equivalent alias/attribute path query. Influencing the generation is as well very difficult since we even can't modify the query | |
OneToMany and cascade delete problem. Anyway - I just modified example (attached to this post). After removing Product, Offer is still in | |
ObjectDB within a resource adapter module and Java EE Connector Architecture https://stackoverflow.com/questions/33790875/how-to-dynamically- modifying -unitname-in | |
WORM (Write once read many) support once they are written. Our questions is, can objectdb be modified to work on such a storage device, ie. hard drive | |
Internal exception when updating date filed (TemporalType.DATE) the posting instructions . Here is your test case in that form. Try to modify it to produce the error | |
Is it possible to remove parent/child entities without refresh? entities. In the following code fragment you can see a modified version of the testRemoveVariant1 | |
Delete object from collection versus delete from JPQL I'm a newbie, so this is a pretty fundamental question. I'm not sure if there is a bi-directional relationship between the objects in memory and ObjectDB. I know I can modify the objects and use persist() to write them to the database. But does running a JPQL update or delete alter | |
Compare old and new schema Hello, I have an old database file with important data. Over time, I have modified some 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 | |
ObjectDB version 2.2 has been released of modified ancestor classes. Fixed a bug in handling indexes in a new ancestor class. Fixed a query | |
combined index not used.parentNode.classIdentifier = "(ME)" order by o.parentNode. modified desc database can be downloaded | |
ObjectDB 2.0.4 Added support for JTA and Java EE Containers ( issue #8 ). Fixed a bug in indexing entity objects. Fixed a bug in fixing broken references in ObjectDB Doctor. Fixed a bug in modifying enhanced detached embedded objects. Fixed a spring transformer (LoadTimeWeaver) problem. Fixed a class | |
ObjectDB 2.6.8 Added JPA XML validation schema files to Maven/JEE objectdb.jar. Added automatic release of pessimistic locks on client-server connection failure. Fixed an OptimisticLockException bug on commit after flushing a removed modified entity object. Fixed a NullPointerExeption on new index building | |
javax.servlet.ServletException: Annotated methods must follow the JavaBeans naming convention. __odbHidden_getPropertyName Enhancer modifies the names of persistent property get and set methods by adding __odbHidden | |
ClassCastException thrown when running count query Ralph Moser mosi0815 Ralph Moser The exception is in code that was modified in the last build 2.3.1_03 | |
ObjectDB 2.6.5 of connections specified in configuration. Fixed optimistic lock exception on removing of a flushed modified | |
ODB-FileWriter holds unecessary entity reference after transaction and entity manager are closed DBVectorStepBlockCollectionImpl was modified and then the transaction will be committed. em.getTransaction | |
ObjectDB 2.6.9 PersistenceUnitInfo. Fixed a bug in removing a modified flushed entity object. |