Internal Website Search

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

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

this. About the slow lazy loading - a test case that demonstrates it is needed to evaluate this. support Support

= GenerationType.AUTO) private Long id; @OneToMany (fetch=FetchType. LAZY ,cascade=CascadeType.ALL, mappedBy

Hi, I have found a strange behavior when merging entities with "mapped by" set on @OneToMany relation. Even if object is fetched with find on the same transaction, merge is very slow. It's because on merge every single relation marked as LAZY is fetch from database. Attached two examples

parent for read only purposes (maybe using dto)? When I load them by parent.getChildren() ( lazy

(); private String text; @OneToMany(/*fetch=FetchType. LAZY , cascade=CascadeType.ALL, */mappedBy

={"linkedObjects.pointingTo.nodePath"}) })   the collection is defined as @OneToMany(fetch=FetchType. LAZY

.class, fetch = FetchType. LAZY ) private List signals = new ArrayList (); @ElementCollection private

the problem. A lazy loaded relationship was not fetched, which was accessed when iterating over the list. ph.schoerkhuber Philipp Schörkhuber

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

simple lists/tables) - even when most relationship fields of an entity are forced lazy .   webel Dr Darren Kelly

lazily, that's why stacktrace looks the way it does. Lazy evaluation of Guava methods

Fixed a critical issue that may cause database corruption ( issue #630 ). Initial attempt to enable navigation through lazy loading from detached objects ( feature request #326 ). Improved  toString of criteria queries to use aliases ( issue #12 7). Fixed automatic variable naming in criteria