Home » Search

About multiplication

81-90 of 200Refresh
JDO Doc
3

javax.jdo.annotations.Joins

and not the field or property level. This allows multiple fields and properties to share the same join
JDO Doc
3

javax.jdo.JDOHelper

. If multiple PMFs with the requested name are found, a JDOFatalUserException is thrown. Parameters
JDO Doc
3

javax.jdo.spi.StateManager

PersistenceCapable instance contains a reference to a StateManager. A StateManager might manage one or multiple
JPA Doc
3

javax.persistence.AssociationOverride

mappings at multiple levels of embedding, a dot (".") notation syntax must be used in the name element
JPA Doc
3

javax.persistence.AssociationOverrides

javax.persistence Annotation AssociationOverrides Target: Classes and fields (including property get methods) Used to override mappings of multiple relationship properties or fields. Example: @MappedSuperclass public class Employee { @Id protected Integer id; @Version
JPA Doc
3

javax.persistence.AttributeOverride

map value. To override mappings at multiple levels of embedding, a dot (".") notation form
JPA Doc
3

javax.persistence.AttributeOverrides

javax.persistence Annotation AttributeOverrides Target: Classes and fields (including property get methods) Used to override mappings of multiple properties or fields. Example: @Embedded @AttributeOverrides({ @AttributeOverride(name="startDate
JPA Doc
3

javax.persistence.EntityManager

. The EntityTransaction instance may be used serially to begin and commit multiple transactions. Returns
JPA Doc
3

javax.persistence.IdClass

javax.persistence Annotation IdClass Target: Classes Specifies a composite primary key class that is mapped to multiple fields or properties of the entity. The names of the fields or properties in the primary key class and the primary key fields or properties of the entity must correspond
JPA Doc
3

javax.persistence.ManyToMany

javax.persistence Annotation ManyToMany Target: Fields (including property get methods) Defines a many-valued association with many-to-many multiplicity. Every many-to-many association has two sides, the owning side and the non-owning, or inverse, side. The join table is specified on the owning