About true

api-jpa

javax.persistence.criteria.Subquery

The Subquery interface defines functionality that is specific to subqueries.(Interface of JPA)

 
forum_thread

Merge with Parent/Child entities not possible

Can you please tell me why the following unit test ends with "[ObjectDB 2.5.7_02] javax.persistence.RollbackException"? ... mappedBy = "parent" , orphanRemoval = true ) @ MapKey ( name = "childName" ) ... ( "d: \\ Temp \\ MergeTest.odb" , true ) ;   ParentEntity parentEntity = new ...

 
forum_thread

Activation Issue

Hi, We bought a site license the yesterday. I ran the activation class this morning. That generated the activation key. I took that key as per the instructions, added it to the objectdb.conf inside the jar, and everything was happy. (this was with 2.3.7). However after a reboot I'm now getting the evaluation license restriction message again at compile time (which was I was seeing before putting the activation key in objectdb.conf). I tried upgrading to 2.3.7_02 and updating objectdb.conf with the activation key, but get the same behaviour. ... = "2kb" /> <recovery enabled = "true" sync = "false" path = "." max = "128mb" /> ... "write" /> <locking version-check = "true" /> <processing cache = "64mb" max-threads = ...

 
forum_thread

JPA vs JDO - which is more efficient for OneToMany queries?

I'm curious about the trade offs between JDO and JPA. Seems to me that JDO will perform better and be statically typed. For example: Assume there are Customers and Orders.... class Order { } It is true, however, that in ORM-based implementations it is more efficient to ... in the above example is more efficient), but that is true for both JPA and JDO ORM-based implementations. By the way, if you ...

 
forum_thread

LAZY @ManyToOne field functions as EAGER

In the code example below (also attached) I would like to understand why I am able to print to console a lazy @ManyToOne field after the entity manager closes. There is a switch DO_VIEW_BEFORE_CLOSE, and when it is true the fields are accessed and output before the finding entity manager closes and as expected both a LAZY @ManyToOne field and an EAGER @ManyToOne field are viewable: b.cLazy:{C}[2]"cLazy"
 b.cEager:{C}[3]"cEager" ... is a switch DO_VIEW_BEFORE_CLOSE, and when it is true the fields are accessed and output before the finding entity manager ... TestLazyManyToOne {   /** * If true the console view of the fields of the entities will be * called after ...

 
forum_thread

Lazy loading does not work - crud takes long

tomee7.0.0SNAPSHOT,objectdb 2.6.4 The OneToMany Entities are filled with 40.000 Records and they have between 20-40 Columns. It takes over 50s to load all Project Enities that contains the OneToMany Relationships. It should be load lazy but i didnt know why the query fetch all the Data. ... = CascadeType . ALL , orphanRemoval = true , mappedBy = "project" , fetch = FetchType . LAZY ... = CascadeType . ALL , orphanRemoval = true , mappedBy = "project" , fetch = FetchType . LAZY ...

 
api-jdo

isNew(pc)

Tests whether this object has been newly made persistent.(Method of javax.jdo.spi.StateManager)

 
api-jpa

Basic.optional

(Optional) Defines whether the value of the field or property may be null.(Annotation Element of javax.persistence.Basic)

 
api-jdo

javax.jdo.identity.ByteIdentity

This class is for identity with a single byte field.(Class of JDO)

 
api-jdo

retrieve(pc, useFetchPlan)

Retrieve field values of an instance from the store.(Method of javax.jdo.PersistenceManager)