Fast Object Database for Java - with JPA/JDO support

About lazy

1-10 of 126 resultsRefresh

Retrieving JPA Entity Objects

is returned. A similar method, getReference, can be considered the lazy version of find: Employee ... using a lazy fetch type: @Entity class Employee { : @ManyToOne(fetch=FetchType.LAZY ... FetchType.LAZY in either @OneToOne or @ManyToOne annotations (currently ObjectDB does not distinguish


Enum Constant javax.persistence.FetchType LAZY Defines that data can be lazily fetched. Since: JPA 1.0

Mapped (Inverse) LAZY @OneToMany vs. Unmapped LAZY @OneToMany

to console a lazy @OneToMany mapped field after a finding entity manager closes. There is a switch DO_VIEW ... /resolved, as one would expect for LAZY: a.listA_mapped:[{A}[4]"ownedElement1", {A}[5]"ownedElement2 ... side of the relationship a.a. Q: Why is the LAZY behaviour different for mapped and unmapped lists ? package com

Problem with @Basic(fetch = FetchType.LAZY)

I have a class where two fields are annotated with @Basic(fetch = FetchType.LAZY ... ; @Basic(fetch = FetchType.LAZY) private String description; @Basic(fetch = FetchType.LAZY ... = FetchType.LAZY hint. Am I doing something wrong? (I am using objectdb-2.3.6_10) tia, Wim wim DC Wim

Possible issue with LAZY Loading

Hi, We need lazy loading for one of our large data sets. When I run currently against both 2.4.2 and 2.4.3_01 the db is always returning everything, including the data marked as Fetch.LAZY. I wrote ... Your observation in #2 is correct - LAZY loading doesn't necessarily mean that the data is inaccessible

LAZY @ManyToOne field functions as EAGER

to console a lazy @ManyToOne field after the entity manager closes. There is a switch DO_VIEW_BEFORE_CLOSE ... and as expected both a LAZY @ManyToOne field and an EAGER @ManyToOne field are viewable: b.cLazy:{C}[2 ... as @ManyToOne(fetch=FetchType.LAZY) ? package com.greensoft.objectdb.test.console; import javax

@OneToMany(fetch = FetchType.LAZY) list is always null

Hello. @OneToMany(fetch = FetchType.LAZY) doesn't work when using EJB or something else related ... ") private int id; @OneToMany(fetch = FetchType.LAZY, cascade = CascadeType.ALL) private List ... > Vladiator Vlad Myachikov A lazy relationship is available

Multi threading on DMOs by lazy loading

It is possible to use lazy loading on fields of attached entities by several threads? Example: class EntityZ { @OneToOne(fetch = FetchType.LAZY) EntityX fieldX; @OneToOne(fetch = FetchType.LAZY) EntityY fieldY; @ElementCollection (fetch = FetchType.LAZY) List

Does ObjectDB support lazy loading?

I'm evaluating ObjectDB 2.0 RC1. Everything works fine except a lazy loading problem. I've a Parent ... support lazy loading, am I right? psfung Samuel Fung ObjectDB does support both lazy and eager loading ... that demonstrates that issue. The following sample program demonstrates lazy loading: package com.objectdb.test

Failed to write the value of field using reflection (error 363) on LAZY fetch

with a query where I have set to use LAZY initalization. It fails when it tries to set a 1:n member (e.g. a Modell has several Artikels) . When I remove the LAZY hint (query.setHint("objectdb.result-fetch", "LAZY");) on the query execution it works. I assume it has to do with the @Transactional

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support