Home » Search

About mappedBy

21-30 of 79 Refresh
JDO Doc
4

javax.jdo.annotations.Order

value: {} Since: JDO 2.1 String mappedBy Name of a field or property in the target class that acts
JDO Doc
4

javax.jdo.annotations.Persistent

value: "" Since: JDO 2.1 String mappedBy Name of the related member in the other class where this value
JDO Doc
4

javax.jdo.annotations.Value

) should be indexed. Default value: "" Since: JDO 2.1 String mappedBy Name of a member in the key class
JPA Doc
4

javax.persistence.AssociationOverride

( mappedBy="contactInfo.phoneNumbers") Collection employees; } Since: JPA 1.0
JPA Doc
4

javax.persistence.OrderBy

{ ... @ManyToMany( mappedBy="students") @OrderBy // ordering by primary key is assumed
Forum
4

Error 363 - Failed to read value of inverse relationship

private String id; @OneToMany( mappedBy="town") private Set events; public ... >(), blockedUserList = new ArrayList (); @ManyToMany( mappedBy = "friendWishList") private List possibleFriends; @ManyToMany( mappedBy = "blockedUserList") private
Forum
4

Left join fetch behaviour doesn't retrieve children?

an attribute with mappedBy to the parent. This just break the test !  Test by yourself by adding / removing the mappedBy on the OneToOne annotation. Note that i don't create any entity on that attribute ... = MyEntityChild2.class)   @OneToOne(targetEntity = MyEntityChild2.class, mappedBy = "myEntity
Forum
4

find() cost unreasonable time!

="parent") protected Nodes parent; @OneToMany( mappedBy="parent",fetch=FetchType.EAGER) protected ... ; @OneToMany( mappedBy="parent",fetch=FetchType.EAGER) protected List Sons; public int getId ... changes to your code: Remove mappedBy="parent" from the definition of Sons:     @OneToMany(fetch
Forum
4

Mapped By Fetch is very Slow

again :( ). Here is the test case : 1- Create 100 000 entities with for each 1 entity with @OneToOne( mappedBy ... .ALL, mappedBy = "myEntity") // Test by adding / remove " mappedBy" public MyEntityChild getEntityChild ... to the child is slower and requires an "inverse" query using the mappedBy attribute. In bidirectional
Issue
4

Unexpected Exception during commit

collections directly with no mappedBy - and it is also much more efficient. Therefore, consider removing the mappedBy definition instead of defining the owner account field. Many thanks for the advice ... have a large number of entities that are not used as a collection, I assumed a mappedBy relationship