About modify
Updating JPA Entity Objects
Explains how to use JPA to delete (remove) entity objects from the database. Modifying existing entity objects that are stored in the database is based on transparent persistence, which means that changes are detected and handled automatically. This page covers the following topics: Transparent ...
Conflicting modifiers .... (javax.persistence.Id, javax.persistence.ManyToOne)
I have two classes a Container type class and another class that is 'contained' by that class. The contained class, CompoundKeyMapItem, represents an alternate implementation of an object held in a Map, and uses a Compound Primary Key. The contained class therefore uses an @IdClass. This all works fine on Eclipselink. However when I try and run this in ObjectDb I get the following error; #1 2011-09-23 10:36 I have two classes a Container type class and another class that is 'contained' by that class. The co ...
Schema Update
Explains how to handle JPA/JDO database schema evolution in ObjectDB. The <schema> configuration element supports renaming packages, classes and fields in ObjectDB databases as a complementary operation to renaming or moving these elements in the IDE during source code refactoring. Only these schema changes are ...
Modifier operations
Hi, Today I was reading about different NoSQL databases. One of those database - MongoDB - has a very nice feature, especially for web applications - modifier operations. The whole trick for those operations is to change some value in object without pulling this object from database. So for example we have class: public class WebVisit { public String url; // key public int visitsCount; } As for now I have to pull this class from database: #1 2011-09-12 18:27 Hi, Today I was reading about different NoSQL databases. One of those database - MongoDB - has a very nic ...
javax.persistence.criteria.CriteriaQuery
The CriteriaQuery interface defines functionality that is specific to top-level queries.(Interface of JPA)
javax.persistence.criteria.Subquery
The Subquery interface defines functionality that is specific to subqueries.(Interface of JPA)
where(restriction)
Modify the query to restrict the query result according to the specified boolean expression.(Method of javax.persistence.criteria.CriteriaQuery)
javax.jdo.spi.StateManager
This interface is the point of contact between managed instances of PersistenceCapable classes and the JDO implementation.(Interface of JDO)
where(restrictions)
Modify the query to restrict the query result according to the conjunction of the specified restriction predicates.(Method of javax.persistence.criteria.CriteriaQuery)
NoResultException: No matching results for a unique query
I am very often getting a "com.objectdb.o._NoResultException: No matching results for a unique query" when modifying my already persisted entities within a transaction. I cannot replicate it however because it happens infrequently. The weird thing is that the entity nevertheless gets comitted perfectly right and all data is correctly written so I have no clue what's going on!?? Here's the stacktrace (copy+paste from debug output): ... within a transaction commit that I've been using to modify something only? I've thought the NoResult* exception should happen ...
