8 | composite index not used in querywe 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<ObjectNode> objectsInCharge = new ArrayList<ObjectNode>(); on running a query like select |
8 | LEFT (OUTER) JOIN problem when mappedBy is defined invoices without items! Only invoices with items. When I remove mappedBy from @OneToMany annotation, LEFT ... (); } } @Entity public class Invoice { @OneToMany(mappedBy = "invoice", fetch= FetchType.EAGER |
8 | LazyInitialization / join fetch the fetch join? If so should I do to all fields of List , ie OneToMany or ... do to all fields of List , ie OneToMany or should also be done for joins ? Grateful. rafael_moreira Rafael |
8 | LAZY @ManyToOne field functions as EAGER would expect b.cLazy to not be still resolved. [By constrast, using this approach an unmapped @OneToMany list is not still viewable, although a mapped @OneToMany list is, which I will discuss in |
8 | How to use JOIN FETCH? javax.persistence.OneToMany; import javax.persistence.Persistence; import javax.persistence ... private long id; private String name; @OneToMany @MapKeyTemporal(TemporalType.DATE |
8 | Object explorer cannot open odb file. ObjectDB many-to-many relationshipI created a data model to test many-to-many relationship with a link table as following (full code in attachement) @Entity public class User { @Id private String code; @OneToMany ... public class Project { @Id private String code; @OneToMany(mappedBy = "project |
8 | PostUpdate collection null, the collection is populated. The collection is eagerly fetched. public class MyEntity { @OneToMany(fetch ... { @Id int id; @OneToMany(fetch=FetchType.EAGER, cascade=CascadeType.PERSIST |
8 | Removing an entity throws exception; @OneToMany(mappedBy = "customer", fetch= FetchType.LAZY) private List<Item> itemList; @OneToMany(mappedBy = "customer", fetch= FetchType.LAZY) private List<OtherItem |
1 | Tracking changes to new collections (in enhancement mode) after flush; @OneToMany (fetch = FetchType.EAGER, cascade = {CascadeType.REFRESH, CascadeType.DETACH }) private ... ; @OneToMany (fetch = FetchType.EAGER, cascade = {CascadeType.REFRESH, CascadeType.DETACH |
1 | NullPointerException on TreeSet load(); emf.close(); } @Entity public static class MyEntity { @OneToMany ... { @OneToMany(cascade=CascadeType.PERSIST, fetch = FetchType.EAGER) Set<MyElement> set |
