About fetch

forum_thread

Error 363 - Failed to read value of inverse relationship

I've got two objects: @Entity public class EEvent { @Id @GeneratedValue(strategy = GenerationType.AUTO) private long id; @ManyToOne(optional=false) private ETown town; public ETown getTown() { return town; } public void setTown(ETown town) { this.town = town; } } And: ... text ;   @ OneToMany ( /*fetch=FetchType.LAZY, cascade=CascadeType.ALL, */ mappedBy = ...

 
issue

Use temporary files to enable very large transactions

We have transactions in which many objects are created. These objects are no longer needed in the current transaction after creation. Unfortunately, we will receive an OutOfMemory exception because the objects are kept in the first level cache of ObjectDB. In the forum thread http://www.objectdb.com/database/forum/921 on post #4 you wrote, that ObjectDB should support very large transactions in further version. Can you implement it that ObjectDB used temporary files? ... level2 = "0" /> <fetch hollow = "false" /> <persist ...

 
issue

Unexpected exception (Error 990) on find

I have a huge amount of inserts/updates and after a about 850.000 Entities I got the following error: ... ;   @ ElementCollection ( fetch = FetchType . EAGER ) @ CollectionTable ...

 
issue

Enhanced classes problem

Hell, we have problem with the OEM enhancement licencing. When we used runtime licencing using machine activation code, everything works fine. But when we enhanced our classes with OEM licence, following errors occurs: ... Info about the field and annotations: @OneToMany(fetch = FetchType.EAGER, mappedBy = "jobInfoId")  // relation is ...

 
forum_thread

locks on pure query activities

analyzing the dynamic behavior we can see from the thread dump that a lot of our threads that are just doing simple queries show locks like these (question is: why there are locks and how could we get rid of that):   log1:   ... "weak" level2 = "4096mb" /> <fetch hollow = "true" /> <persist serialization = ...

 
forum_thread

Explorer in 2.3

First, the new Explorer in ObjectDB is fantastic! This is exactly what we've needed - an easy way to do ad-hoc JPQL queries and navigate through the results and even make small changes to primitive data and Strings. After playing with it for a while, here is a list of additional features I'd love to have: 1. Export of selected data: a. Simple - Select a range of cells or a column header and copy text to the clipboard or save to a file (csv, html, etc..). (There appear to be copy menu options, but I cannot get them to work.) ... Then at the bottom of the table or tree, have a link to fetch the next N. This should also apply to collections that are opened ...