Home » Search

About mappedBy

41-50 of 80Refresh
Forum
2

JPA vs JDO - which is more efficient for OneToMany queries?

me see if I grok this. Using JPA: @Entity class Customer { @OneToMany(mappedBy="customer ... impressive. I used JPA, and the @OneToMany(mappedBy="") on the collection was handled entirely implicitly! dmoshal
Forum
2

Lazy loading does not work - crud takes long

= CascadeType.ALL, orphanRemoval = true, mappedBy="project",fetch = FetchType.LAZY)     private List datapoint;         @OneToMany(cascade = CascadeType.ALL, orphanRemoval = true, mappedBy
Forum
2

NoSuchFieldError: __odbTracker on NetBeans 7.3 + JBoss 7.1.1

(mappedBy = "owner") private List cities; private String name; public String ... serialVersionUID = 33L; @OneToMany(mappedBy = "city") private List persons
Forum
2

Object explorer cannot open odb file. ObjectDB many-to-many relationship

(mappedBy = "user") @MapKey     private Map assignements; } @Entity public class Project {     @Id     private String code;         @OneToMany(mappedBy = "project
Issue
2

Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct)

= new ArrayList(); @OneToMany(mappedBy = "owner", cascade = CascadeType.ALL) public ... before detachment The easiest way is to set the fetch type to EAGER: @OneToMany(mappedBy = "owner
Forum
2

OneToMany and cascade delete problem

): @Entity public static class Store { @OneToMany(targetEntity = Offer.class, mappedBy = "store ... { @OneToMany(targetEntity = Offer.class, mappedBy = "product", fetch = FetchType.LAZY, cascade = CascadeType
Forum
2

Performance in large transactions

{         @OneToMany(cascade = CascadeType.ALL, mappedBy = "ownerEntity")         private List ... = CascadeType.ALL, mappedBy = "ownerEntity")         private List list = new ArrayList
Forum
2

Problem persisting a TreeSet field

relationship: @ManyToOne private Message parent; @OneToMany(mappedBy = "parent") private TreeSet ... an inverse field - remove he mappedBy setting, and update the TreeSet explicitly - ObjectDB doesn't need
Forum
2

Relationships and tracking changes

.ALL, mappedBy="VERLAG_ID") private List users; Table "EBUser": @Entity(name="USER") public class ... ignores ORM annotations such as @Column and JoinColumn. Therefore, Java field names should be used in mappedBy. See also this manual page. caitanya
Forum
2

Removing an entity throws exception

; @OneToMany(mappedBy = "customer", fetch= FetchType.LAZY) private List itemList; @OneToMany(mappedBy = "customer", fetch= FetchType.LAZY) private List