About fetch

release

2.2.1

... . Fixed several bugs in handling eager fetch. Fixed a pessimistic locking bug . ...

 
issue

JPQL support for Maps (JPA 2.0)

JPQL 2.0 introduces the ability define FROM variables for map keys and values. Currently ObjectDB supports FROM variables for collection elements and FROM variables for map keys and values are expected to be supported in future versions. ... ... @ ElementCollection ( fetch = EAGER ) @ Column ( name = ...

 
forum_thread

OneToMany and cascade delete problem

Hi, I don't really know if this is a bug or maybe model that I make is bad. I have a problem with with two different classes with OneToMany relation to one, shared class. For example (first class): @Entity public static class Store { @OneToMany(targetEntity = Offer.class, mappedBy = "store") private List<Offer> offers; } second class: ... = Offer. class , mappedBy = "product" , fetch = FetchType . LAZY , cascade = CascadeType ...

 
api-jdo

clearGroups()

Remove all active groups leaving no active fetch group.(Method of javax.jdo.FetchPlan)

 
forum_thread

Selective merge/cascade of detatched entity

I'm having an issue with my application, and I'm hoping you guys will be able to help. Please forgive typos and obvious errors, I'm having to retype from a non-internet connected network. A contrived example is: ... String name ;   @ OneToMany ( fetch = FetchType . EAGER , cascade = CascadeType . ...

 
forum_thread

LEFT (OUTER) JOIN problem when mappedBy is defined

Hi all, I want to get objects with their lists, even when the lists are empty. So I've witten this query: "SELECT i FROM Invoice i LEFT OUTER JOIN i.itemList items" But this query never returns invoices without items! Only invoices with items. When I remove mappedBy from @OneToMany annotation, LEFT JOIN works correctly. Is this normal behaviour? Thank you Michael   Sample application ... OneToMany ( mappedBy = "invoice" , fetch = FetchType . EAGER , orphanRemoval = true , ...

 
api-jdo

getFetchGroup(cls, name)

Create an unscoped, modifiable FetchGroup for the Class and name.(Method of javax.jdo.PersistenceManagerFactory)

 
forum_thread

Mysterious "Attempt to persist a reference to a non managed instance" error

I've been working with ObjectDB for the past several months, and it's behaved pretty much as expected. I made a few modifications to a working set of classes today, and it's started throwing exceptions at commit time. I've stripped it down to a  set of files that seem to be of trivial complexity, but it's still failing. It involves two entities, Index and Ostrich. The thing to note is that the Index structure is recursive through maps; but that's never caused any problem for me in the past. ... long id ; @ OneToOne ( fetch = EAGER , cascade = PERSIST ) public Ostrich ...

 
forum_thread

ObjectDB 2.6.9_06 (embedded): Cascading merge resulting in duplicate objects

This issue maybe related to issue #110 (http://www.objectdb.com/database/issue/110). Because that issue has been closed as "fixed", I am reporting this new issue. This is my class definition: ... {   @ OneToMany ( fetch = FetchType . EAGER , cascade = CascadeType . ...

 
api-jdo

fetchStringField(fieldNumber)

Fetch one field from the field manager.(Method of javax.jdo.spi.PersistenceCapable.ObjectIdFieldSupplier)