12 | Composite indexes? @OneToOne, @ManyToOne? I don't want to start with complex example, so maybe I'll try to explain ... field used also on relations? @OneToOne, @ManyToOne? Yes. They are useful when the query includes |
12 | Problem with @Basic(fetch = FetchType.LAZY) wim DC Wim De Clercq So I replaced my original code with @OneToOne(fetch = FetchType.LAZY, cascade = CascadeType.ALL) private LargeString description; @OneToOne(fetch = FetchType.LAZY |
12 | Extra uninitialised entities spawned on merge() with a relationship @OneToOne Element child. package test; import java.util.*; import javax.persistence ... "); addOwnedElement(child); } private Element child; @OneToOne |
12 | Upgrade to 2.4.1_01 our code for 2.3.7_18, we had @OneToOne(cascade=CascadeType.ALL, fetch=FetchType.EAGER ... .objectdb.o.EMR.q(EMR.java:79) at com.objectdb.jpa.EMImpl.merge(EMImpl.java:451) ... 24 more @OneToOne |
12 | Mysterious "Attempt to persist a reference to a non managed instance" error javax.persistence.ManyToMany; import javax.persistence.OneToOne; import static javax.persistence ... Serializable { @Id @GeneratedValue private long id; @OneToOne(fetch=EAGER, cascade |
8 | Using of Second Level Cache MyEntity1 { @OneToOne private MyEntity2 myEntity2; @OneToMany private List<MyEntity3> list; } btc_es |
8 | Are indexes implicitly created for relationships?Do the following annotations @OneToMany @ManyToOne @ManyToMany @OneToOne imply @Index ? Thanks, Carl FastModel Ben Schreiber Actually these annotations (except @ManyToMany) should apply @Unique on the @One side. But ObjectDB doesn't apply these indexes automatically, because of their overhead |
2 | Tracking changes to new collections (in enhancement mode) after flush.FIELD) @Column (name = "uid") private String uid; @OneToOne (fetch = FetchType.EAGER ... MappingImpl { @Id private String uid; @OneToOne (fetch = FetchType.EAGER |
2 | Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct) @OneToOne relationship fields that likewise become null: private List<Element> ownedElements = new ... and @OneToOne fields are also null). In all cases lists that are given in the explored database |
2 | New entity objects are duplicated on merge cascading A { @Id @GeneratedValue long id; @OneToOne(fetch = FetchType.LAZY, cascade ... ; @OneToOne(fetch = FetchType.LAZY, cascade = CascadeType.ALL) C c; } @Entity public |
