7 | Is there any restriction when using fetch=FetchType.LAZY ? object declaration @OneToMany(fetch=FetchType.EAGER, cascade = CascadeType.ALL) private ... @OneToMany(fetch=FetchType.LAZY, cascade = CascadeType.ALL) private LinkedList<OdbObject |
7 | Foreign key constraint issue private long id; @ManyToOne(optional = false, cascade = {}) @JoinColumn(name="PARENT_ID", nullable ... = parent;} } @Entity public class Parent { @Id @GeneratedValue private long id; @OneToMany(cascade |
7 | Lazy loading does not work - crud takes long, generator = "PROJECT_SEQUENCE") private Long id; .. .. @OneToMany(cascade ... <Datapoint> datapoint; @OneToMany(cascade = CascadeType.ALL, orphanRemoval = true, mappedBy |
7 | OEM enhancingHello, I have question regarding OEM licence enhancement. @OneToMany(fetch = FetchType.EAGER, cascade = CascadeType.ALL) private SomeClass[] props; @OneToMany(fetch = FetchType.EAGER, cascade = CascadeType.ALL) private Map<String, SomeClass2> vars = new TreeMap<String, SomeClass2 |
7 | Extra uninitialised entities spawned on merge() ArrayList<Element>(); @OneToMany(mappedBy = "owner", cascade = CascadeType ... , whereas others might thown an exception immediately. The merge() operation can be optionally cascaded in these cases |
7 | Upgrade to 2.4.1_01 our code for 2.3.7_18, we had @OneToOne(cascade=CascadeType.ALL, fetch=FetchType.EAGER ... .visitRefs(CLT.java:160) at com.objectdb.o.TVS.j(TVS.java:169) at com.objectdb.o.TVS.cascade(TVS.java |
7 | Cannot sort descending, when ordering by caluculated float in a method { @OneToMany(cascade=CascadeType.PERSIST) private List<InvoiceItem> itemList = new ArrayList ... = "invoice", fetch= FetchType.EAGER, orphanRemoval=true, cascade= CascadeType.ALL) private List |
5 | _PersistenceException: Type is not found on getSingleResult.", cascade = CascadeType.ALL, orphanRemoval = true) private List<Acudiente> acudientes; public |
5 | Problem on JPA Merge Entity.Hello, I have a problem with the EntityManager.merge() function. I set a property value of an entity (statement) with an other entity (newSingleConstraint). newSingleValue is already persisted. I do this myself (no use of cascade because sometimes the newSingleValue is already in database |
1 | Unexpected Exception during commit.j(TVS.java:169) at com.objectdb.o.TVS.cascade(TVS.java:156) at com.objectdb.o.STA ... to the stack trace, during commit an attempt to cascade persist through an inverse (mapped by) collection |
