8 | "Unexpected query expression" using CriteriaQuery FetchParent Interface(Person.class); root.fetch("PersonData"); //@OneToOne relationship criteriaQuery.select(root |
8 | openejb jpa jaas module; @OneToOne private Settings settings; private String phoneNumber; @OneToMany |
8 | Accessiblity of attributes in entities in several OSGi-Bundles MessageImpl { @OneToOne private ModelElementImpl e; @Basic private String |
8 | Global way to set Lazy-loading fetch functionality for all the fieldsHi, for cascading persist, I have 3 choices: - Either locally (@OneToOne(cascade=CascadeType.PERSIST)) - Either at objectdb level (<cascade-persist always="auto" on-persist="false" on-commit="true" />) - Either at JPA global level (orm.xml). For defining fetch policy, I know the local way |
8 | EM.find() is suddenly slower (AccessType.FIELD) @Column (name = "uid") private String uid; @OneToOne (fetch |
8 | @Column( name = "columnName") doesn't work" ) private List<AfwDataKeyItem> dataItems; @OneToOne(fetch = FetchType.LAZY, cascade |
8 | NOT NULL not workingI added a OneToOne Realtionship to one of my entity classes. To give this field a value in my existing datasets i wrote an upgrade method. The cool thing is that SELECT u FROM Unit u WHERE u.lastPosition IS NOT NULL returns no datasets. Is this a bug or am i missing something? mosi0815 Ralph |
8 | LAZY @ManyToOne field functions as EAGER lazy loading in these cases. Regarding your example, ObjectDB can use lazy loading in OneToOne |
8 | Embedded Entity in EmbeddedId not persisted. Error 631 at select. CascadeType.PERSIST: @Embeddable public static class AId { @OneToOne(cascade |
1 | com.objectdb.o.InternalException: null PersistableObject { @OneToOne(mappedBy = "spouse") private Customer spouse = null; private |
