1 | javax.persistence.ManyToOne: @ManyToOne(optional=false) @JoinColumn(name="CUST_ID", nullable=false, updatable=false) public |
1 | getSingleResult() query language UPDATE or DELETE statement QueryTimeoutException - if the query execution exceeds |
1 | getResultList()Method javax.persistence.Query List getResultList() Execute a SELECT query and return the query results as an untyped List. Returns: a list of the results Throws: IllegalStateException - if called for a Java Persistence query language UPDATE or DELETE statement QueryTimeoutException - if the query |
1 | getSingleResult() language UPDATE or DELETE statement QueryTimeoutException - if the query execution exceeds the query |
1 | javax.persistence.OneToOne=true, nullable=false, updatable=false) public CustomerRecord getCustomerRecord() { return |
1 | getResultList()Method javax.persistence.TypedQuery List<X> getResultList() Execute a SELECT query and return the query results as a typed List. Returns: a list of the results Throws: IllegalStateException - if called for a Java Persistence query language UPDATE or DELETE statement QueryTimeoutException |
1 | Memory leak in com.objectdb.o.CST seem to have alot more spikes than usual. My server's graph is usually fairly flat before this update. Perhaps there is some performance tradoff with this update to save memory usage? In the attached ... it and compare it to objectdb-2.8.3_05(my prior version before this update |
0 | javax.jdo.InstanceCallbacks that might have been affected by modified non-persistent fields should be updated in this method. This method is modified |
0 | javax.jdo.FetchGroup member. Fetch groups are updated using methods on this interface. An instance of a class |
0 | javax.jdo.listener.StoreCallback should be updated in this method. This method is modified by the enhancer so that changes |
