ObjectDB Database Search

; and You must cause any modified files to carry prominent notices stating that You changed the files ... are for informational purposes only and do not modify the License. You may add Your own attribution notices ... the Work, provided that such additional attribution notices cannot be construed as modifying the License

either the Java transient modifier (which also affects serialization) or the JPA @Transient ... that modifies an entity, its version number is automatically incremented by one. Version fields are used

when the EntityManager detects that an entity has been modified . @PostUpdate : Invoked after an entity

, which modify the database. For debugging query failures, you might need to record "all" operations to reproduce

entities. Because operations that modify the database require an active transaction, persist throws

phenomena can occur: P1 (Dirty read): Transaction T1 modifies a row. Another transaction T2 then reads that row and obtains the modified value, before T1 has committed or rolled back. Transaction T2 ... T2 then modifies or deletes that row, before T1 has committed. Both transactions eventually commit

to perform operations that affect the state of the persistence context, or that modify the lifecycle state ... manager. Modifying the contents of the returned map does not change the configuration in effect

that modify the database require an active transaction. An exception is also thrown if the argument ... , and so on. Once assigned, the object ID cannot be modified or replaced. It represents the object as long as ... and finally returned to the application. Persistent objects that have not been modified or deleted

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CollectionJoin CollectionJoin on (    Expression restriction ) Modify the join to restrict the result according ... . Parameters: restriction - a simple or compound boolean expression Returns: the modified join object. Since: Jakarta Persistence (JPA) 2.1

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CollectionJoin CollectionJoin on (    Predicate... restrictions ) Modify the join to restrict the result according ... . Parameters: restrictions - zero or more restriction predicates Returns: the modified join object. Since: Jakarta Persistence (JPA) 2.1

whether they must be retained Returns: the modified query. Since: Jakarta Persistence (JPA) 1.0

persisted object.  Attempt to modify an object with no active transaction ... to modifi de object in DB, just sort it to show at the moment. someone can help me ?   thanks David ... when a managed entity object is modified and no transaction is active. Please follow the exception stack

new and modified Chapters being persisted and merged accordingly. This works as expected on the Book ... . Burabari Burabari Kpai The following are modified for the working case where new Chapters are added ... would have double entry of same record. Burabari Burabari Kpai For completeness, attached is the modified sample

time, stopping the program, and modifying code for extended time and all variations in between

ticket was getting an exception with the error message "Attempt to modify a primary key of a managed

{ support Support I've added the listener class and modified my servlet class (which is a REST

Hi, I'm working on some reporting stuff in our application. One of few different reports should include activity on last modified objects. The query for now looks like this: select date(insp.lastModificationDate), insp.modifiedBy, insp.description.length(), insp.products.size(), insp.picture from

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

query. Influencing the generation is as well very difficult since we even can't modify the query

above, but instead of a modified embedded object we have an embedded collection. Build 2.6.1_02 should fix this issue. If the exceptions in your application are due to modifying a persistent collection

only. This happens automatically if you try to access the replicated database with new or modified ... No immediate fix is currently planned. The workaround is to make sure that every new (or modified ) type

has been modified by an UPDATE query. By using clear , you clear all cached objects from the EntityManager

.parentNode.classIdentifier = "(ME)" order by o.parentNode. modified desc database can be downloaded

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

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

Enhancer modifies the names of persistent property  get and set methods by adding __odbHidden