Internal Website Search
71-80 of 200 resultsRefreshIs it ok to put list or map of embeddable objects in entity ? { (...) @OneToMany(cascade = CascadeType.ALL) List<EntityC> entityCList; } cascade ... ; (...) @OneToMany(cascade = CascadeType.ALL) List | |
Remove not working) at com.objectdb.o.TVS.cascade(TVS.java:156) at com.objectdb.o.TVS.g(TVS.java:105) at com.objectdb.o ... A { @OneToMany(mappedBy="a", cascade=CascadeType.REMOVE) private List<B> ... > The exception is thrown because the removal of A is cascaded to removal of a B instance | |
Multiple Collection Fields not update correctly; @OneToOne(cascade = CascadeType.ALL) EntityA entityA; EntityA: @OneToOne(cascade = CascadeType.ALL) EntityB entityB; If I make only one of the cascade, then this bug | |
Performance in large transactions floats; } @Entity public static class MyEntity { @OneToMany(cascade = CascadeType ... ; @OneToMany(cascade = CascadeType.ALL, mappedBy = "ownerEntity")   ... ; @OneToMany(cascade = CascadeType.ALL, mappedBy = "ownerEntity")   | |
Global way to set Lazy-loading fetch functionality for all the fields Hi, 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 | |
Persisting collection where members are subclasses/persistence/store#cascading_persist">cascading persist is enabled (it is enabled by default ... ; String name; @OneToMany(cascade | |
significant performance decrease="false" /> <cascade-persist always="auto" on-persist="false" on-commit="true" /> < ... ArrayList<ObjectNode>(); @OneToMany(fetch=FetchType.LAZY,cascade=CascadeType.REMOVE ... ;ObjectNode>(); @OneToMany(fetch=FetchType.LAZY,cascade=CascadeType.REMOVE) public List< | |
Dirty checking> What's the best way to cascade persistence of Entities contained by other Entities (i.e ... > Please use a new forum thread to discuss cascading, as it is not directly related to the subject ... > will move cascading discussion to a new thread. thanks dmoshal David Moshal | |
Updating Entities other. Which is where my question comes in... How do I ensure that any changes done to paygradeDB cascade into ... the databases when there is a modification made that needs to cascade throughout the entire application ... weren't cascading as I had expected them to. I came up with this idea and it worked... | |
NullPointerException when using multithreading secondId; @OneToOne(cascade=CascadeType.ALL) private HashMap<String, EmbeddableA> myMap; } @Embeddable public class EmbeddableA { @OneToOne(cascade=CascadeType ... { @OneToOne(cascade=CascadeType.ALL) private HashMap<String, Object> myMap; } |