About true

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 ...

 
issue

[ObjectDB 2.2.5_02] Unexpected exception (Error 990) com.objectdb.o.InternalException: java.lang.NullPointerException: null

reporting issue as requested  ... { return findChartEntities ( true , - 1 , - 1 ) ; }   ... ; this . reverseOrder = Boolean. TRUE ; }   @ EmbeddedId public ...

 
issue

Explorer bug ? Objects seem to be missing from database in Class view, but are present as references

objectdb-2.2.5_08 NetbeansID6.9.1+Glassfish3.01 I suspect the following is an Explorer bug. It is marked knowingly as CRITICAL by me because it makes the ObjectDB system unusable for a real project because it appears to be either database integrity corruption, or it just looks like it, which is just as bad. I attach a running project illustrating the problem, as well as screenshots. ... [null](TEST: A readonly fixed true Boolean value) INFO: RequestBean []: Persisted: ... [64](TEST: A readonly fixed true Boolean value) INFO: RequestBean []: Updated: ... [64](TEST: A readonly fixed true Boolean value) INFO: RequestBean []: Created: ...

 
forum_thread

Extra uninitialised entities spawned on merge()

In the following, Element is a base entity class, with a bi-directional @ManyToOne-@OneToMany relationship Element owner - List<Element> ownedElements, and Example is a subclass entity with a relationship @OneToOne Element child. ... static boolean DO_PERSIST_BEFORE_MERGE = true ;   /** * @param args the command line arguments ...   Case: DO_PERSIST_BEFORE_MERGE = true: If I create an Element 'root', persist it, load ...

 
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

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

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 ...

 
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 ...

 
api-jpa

javax.persistence.criteria.Subquery

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

 
issue

Sort of very large objects - out of memory

The attached test is failing with an out of memory exception when running with -Xmx512m It performs the following actions: 1) Create 5 persist threads which create and persist a large object in a loop 100 times each 2) Create 5 get threads which read 100 objects each in a loop based on object creation time and priority The message size should be around 1mb so I think there should be around 11mb of "live" data in play at any time. The objectdb cache settings are low in the config - database section is below for reference. ... = "2kb" /> <recovery enabled = "true" sync = "false" path = "." max = "128mb" /> ... "write" /> <locking version-check = "true" /> <processing cache = "8mb" max-threads = ...