ObjectDB Database Search

(name = "KEY_DESCRIPTOR") private AfwKeyDescriptor keyDescriptor; @OneToMany(fetch = FetchType. LAZY ... = FetchType. LAZY , cascade = CascadeType.ALL) private AfwCodedDataBlock codedDataBlock; private int level

are executed in the Explorer in a special lazy mode, which is faster in returning the results ... ;  query.setHint("objectdb.result-fetch", " LAZY "); support Support Thank you, is where any

; ... @OneToMany(fetch=FetchType. LAZY ) public Set workflow = new HashSet (); When we remove an object ... remaining sceleton is still in the database and loaded by a subsequent lazy loading ? hgzwicker Hans

{ @MapsId @ManyToOne(fetch = FetchType. LAZY ) private Merchant merchant; @MapsId @ManyToOne(fetch = FetchType. LAZY ) private List stores; // Setter/Getter } So I wanted to add index on Customer for merchant

(mappedBy = "customer", fetch= FetchType. LAZY ) private List itemList; @OneToMany(mappedBy = "customer", fetch= FetchType. LAZY ) private List otherItemList; ... getters and setters } Only address is filled

(queryString, MyEntity.class); q.setHint("objectdb.result-fetch", " LAZY "); List firstQueryResult = q ... .setHint("objectdb.result-fetch", " LAZY "); List secondQueryResult = outerQuery.getResultList

Given that the default seems to be FetchType. LAZY for all collections @OneToMany and @ManyToMany. Such as a configuration option. Instead of having to explicitly set fetch in annotation code in every relationship. webel Dr Darren Kelly No. There is no such configuration option, since having EAGER

(targetEntity = Product.class, fetch = FetchType. LAZY ) private List products; There is only 680

to LAZY . By doing that you instruct ObjectDB to return object IDs rather than full objects in query

Hi, I'm trying to persists objects defined as follows: @Entity @Inheritance(strategy = InheritanceType.SINGLE_TABLE) public abstract class AbstractContainer { ... @OneToMany(fetch = FetchType. LAZY , mappedBy="parent") private Set abstractContainers = com.google.common.collect.Sets

hint and check if it helps:  query.setHint("objectdb.result-fetch", " lazy

a (mostly) LAZY -only fetch policy across the system. Most of my EJB methods for querying are configurable

, rather than the annotated fields, as shown on the first post. Sorry, excuse lazy copy-and-paste

.       harald77 Harald The null and 0 values may be the result of lazy loading

;(...)     @ManyToMany(targetEntity = Product.class, fetch = FetchType. LAZY )   

("objectdb.result-fetch", " LAZY ");     return q.getResultList(); } btc_es BTC

= Offer.class, mappedBy = "product", fetch = FetchType. LAZY , cascade = CascadeType.ALL) private Set offers

. LAZY ) public Set getEmployees() { return employees; } public void setEmployees(Set employees

) @ElementCollection private Map values = new HashMap (); @OneToOne (fetch = FetchType. LAZY , cascade

". If you use version 2.3.4 then the output is "username". I think lazy fetching of primitive fields is a bit

") @GeneratedValue(strategy = GenerationType.AUTO) private Long id; @OneToMany (fetch=FetchType. LAZY ,cascade

: @OneToMany(cascade = {CascadeType.ALL}, fetch = FetchType. LAZY /*, mappedBy = "person"*/) private Set

we defined a composite index for class Action: @Index(name="ssst",members={"startDate","state","subType","type"}) and an index for the OneToMany @OneToMany(fetch=FetchType. LAZY ) @Index public List objectsInCharge = new ArrayList (); on running a query like select count(a) from Action a JOIN

Lai Yang Maybe you are trying to load the entire tree into memory. Try replacing EAGER with LAZY

Hi there, The upgrade to 2.4.1_02 fixed the initial problem, however there still seems to be an issue. To me it appears that Embeddable might be being lazy loaded, but I cannot be sure. I have attached a testcase demonstrating this issue. Its failing on the merge. Thanks P. pedwards Paul Edwards

objectdb.java.util.ArrayList cannot be disabled, as it is an essential feature that enables lazy partial

{ @ManyToOne (targetEntity = DataTypeImpl.class, cascade = {CascadeType.ALL }, fetch = FetchType. LAZY

, but I think still being better than using non- lazy data. elnll002 Facundo Curti

getSingleton() { return container; } } @ManyToOne(fetch=FetchType. LAZY ) @Id private Container container

. Meanwhile, you can run the query in LAZY mode , and then data from the database will be retrieved in batches

is faster at runtime. It could be due to the different default fetch value ( LAZY for 

;   @MapsId     @ManyToOne(fetch = FetchType. LAZY )    

with the new index with no need for further data retrieval. Another option that can be checked is running the query with lazy fetch . support Support

are the exact rules how to attach detached entities when the entity manager uses lazy loading

we did setup automated tests for our system and it seams that in around 1 of 100 cases the update of a one to many collection is not working. Definition: @OneToMany(fetch=FetchType. LAZY ) @Index public List childNodes = new ArrayList (); change of the childNodes within a transaction (a newly

with query option: query.setHint("objectdb.result-fetch", " LAZY "); btc_es BTC EmbeddedSystems The exception

= FetchType. LAZY ) private List languages; public final int getGid() { return gid; } public final void

. One example is in: Does ObjectDB support lazy loading?   which has initialisation of instance

on an attempt to use a lazy collection that has not been loaded in a detached entity object. Build 2.3.1_03 ... is included now in build 2.3.2_01. Lazy collections will always hold a strong reference to the containing

{   @OneToMany(fetch = FetchType. LAZY , cascade = CascadeType.ALL, orphanRemoval = true)  

Added support of lazy loading of mapped by (inverse) singular relationships ( issue #768 ). Added support for using ObjectDB with TomEE / OpenEJB . Improved loading of eager mapped by (inverse) relationships ( issue #769 ). Improved performance of database file extending. Fixed a bug in ignoring

Fixed a bug in lazy loading of instances of non enhanced classes. Fixed a bug in using the Replayer with no updates to the database. Fixed an activation bug.

a transaction without lazy loading? Best regards btc_es BTC EmbeddedSystems @NamedEntityGraph is currently not

As demonstrated in this forum thread , a mapped by collection field with lazy fetch mode is not initialized in results of a query that uses JOIN FETCH on that collection field (when enhancement is used). support Support   Build 2.4.1_06 fixes this issue (fields are now initialized

Fixed a bug in query execution optimization ( issue #2170 ). Fixed cascading delete through unloaded ( lazy ) relationships. Fixed a NullPointerException when using "objectdb.temp.page-file" ( issue #2163 ) Added logging and suspend exception for  issue #2153 . Fixed a bug in using SIZE with

object. Fixed a bug in lazy loading of instances of non enhanced classes. Added Explorer support of ID