ObjectDB Database Search

Access to client/server database from multiple applications

multiple different applications access one odb file

Multiple Collection Fields not update correctly

Multiple @ID

Multiple MEMBER OF query

has inheritance, multiple subgraphs can be specified. These additional subgraphs are intended to add ... of the corresponding NamedSubgraph element. If multiple key subgraphs are specified due to inheritance ... to that NamedSubgraph definition. If the target type has inheritance, multiple subgraphs can be specified

JPA Annotation SecondaryTables Target: TYPE Implemented Interfaces: Annotation Specifies multiple secondary tables for an entity. Example 1: Multiple secondary tables assuming primary key columns ... : Multiple secondary tables with differently named primary key columns. @Entity @Table(name="EMPLOYEE

conversion mappings at multiple levels of embedding, a dot (".") notation form must be used in ... for this element must be specified if multiple converters would otherwise apply. Since: JPA 2.1 boolean

to a managed type with inheritance. This allows for multiple subclass subgraphs to be defined ... for multiple subclass subgraphs to be defined for this node of the entity graph. Subclass subgraphs

is used to refer to that NamedSubgraph definition. If the target type has inheritance, multiple subgraphs ... . If multiple subgraphs are specified due to inheritance, they are referenced by this name. Since: JPA 2.1

attribute also being specified. If the target type has inheritance, multiple subgraphs can be specified ... as specified by the name element of the corresponding NamedSubgraph element. If multiple key

that the data for the entity class is stored across multiple tables. If no SecondaryTable annotation ... with multiple primary key columns. @Entity @Table(name="CUSTOMER") @SecondaryTable(name="CUST

a node to the graph that corresponds to a managed type with inheritance. This allows for multiple ... type with inheritance. This allows for multiple subclass subgraphs to be defined for this node

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

JPA Annotation AssociationOverrides Target: TYPE, METHOD, FIELD Implemented Interfaces: Annotation Used to override mappings of multiple relationship properties or fields. Example: @MappedSuperclass public class Employee { @Id protected Integer id; @Version protected Integer version; @ManyToOne

value. To override mappings at multiple levels of embedding, a dot (".") notation form must be used

JPA Annotation AttributeOverrides Target: TYPE, METHOD, FIELD Implemented Interfaces: Annotation Used to override mappings of multiple properties or fields. Example: @Embedded @AttributeOverrides({ @AttributeOverride(name="startDate", column=@Column("EMP_START")), @AttributeOverride(name="endDate

JPA Annotation Attribute in javax.persistence.Convert Class converter default void.class Specifies the converter to be applied. A value for this element must be specified if multiple converters would otherwise apply. Since: JPA 2.1

JPA Annotation Converts Target: METHOD, FIELD, TYPE Implemented Interfaces: Annotation Used to group Convert annotations. Multiple converters must not be applied to the same basic attribute. See Also: Convert Since: JPA 2.1 Public Annotation Attributes Convert [] value default null The Convert mappings that are to be applied. Since: JPA 2.1

JPA Method in javax.persistence.EntityGraph Subgraph addSubgraph (    Attribute  attribute,    Class  type ) Add a node to the graph that corresponds to a managed type with inheritance. This allows for multiple subclass subgraphs to be defined for this node

JPA Method in javax.persistence.EntityGraph Subgraph addSubgraph (   String attributeName,    Class  type ) Add a node to the graph that corresponds to a managed type with inheritance. This allows for multiple subclass subgraphs to be defined for this node

. The EntityTransaction instance may be used serially to begin and commit multiple transactions. Return

JPA Method in javax.persistence.EntityManager EntityTransaction getTransaction () Return the resource-level EntityTransaction object. The EntityTransaction instance may be used serially to begin and commit multiple transactions. Return: EntityTransaction instance Throws: IllegalStateException - if invoked on a JTA entity manager Since: JPA 1.0

JPA Annotation IdClass Target: TYPE Implemented Interfaces: Annotation 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

JPA Annotation ManyToMany Target: METHOD, FIELD Implemented Interfaces: Annotation Specifies 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

JPA Annotation ManyToOne Target: METHOD, FIELD Implemented Interfaces: Annotation Specifies a single-valued association to another entity class that has many-to-one multiplicity . It is not normally necessary to specify the target entity explicitly since it can usually be inferred from the type

JPA Annotation NamedNativeQueries Target: TYPE Implemented Interfaces: Annotation Specifies multiple native SQL named queries. Query names are scoped to the persistence unit. The NamedNativeQueries annotation can be applied to an entity or mapped superclass. See Also: NamedNativeQuery Since: JPA 1

JPA Annotation NamedQueries Target: TYPE Implemented Interfaces: Annotation Specifies multiple named Java Persistence query language queries. Query names are scoped to the persistence unit. The NamedQueries annotation can be applied to an entity or mapped superclass. See Also: NamedQuery

JPA Annotation NamedStoredProcedureQueries Target: TYPE Implemented Interfaces: Annotation Specifies multiple named stored procedure queries. Query names are scoped to the persistence unit. The NamedStoredProcedureQueries annotation can be applied to an entity or mapped superclass

mappings, as defined by the SqlResultSetMapping annotation. If there are multiple result sets

JPA Annotation OneToMany Target: METHOD, FIELD Implemented Interfaces: Annotation Specifies a many-valued association with one-to-many multiplicity . If the collection is defined using generics to specify the element type, the associated target entity type need not be specified

JPA Annotation OneToOne Target: METHOD, FIELD Implemented Interfaces: Annotation Specifies a single-valued association to another entity that has one-to-one multiplicity . It is not normally necessary to specify the associated target entity explicitly since it can usually be inferred from the type

the most general case ( multiple result sets and/or update counts, possibly also in combination

. This allows unambiguous identification of the field to be marked dirty. If multiple classes declare ... this method to ask the instance to provide the values of the multiple fields identified by fieldNumbers. Parameters: fieldNumbers - the fields whose values are to be provided by multiple callbacks

with a PersistenceManager . Multiple queries might be executed simultaneously by different threads, but the implementation ... of the subquery execution. If the same value of variableDeclaration is used to add multiple ... setExtensions (Map extensions) Set multiple extensions, or use null to clear all extensions. Map

multiple exceptions in the runtime. If multiple objects caused the problem, each failed object

[] getNestedExceptions () The exception may have been caused by multiple exceptions in the runtime. If multiple objects caused the problem, each failed object will have its own Exception . Return

JDO Method in javax.jdo.JDOException Throwable[] getNestedExceptions () The exception may have been caused by multiple exceptions in the runtime. If multiple objects caused the problem, each failed object will have its own Exception . Return: the nested Throwable array. Since: JDO 1.0

() The exception may have been caused by multiple exceptions in the runtime. If multiple objects caused

. This will be the case of inheritance, where multiple PersistenceCapable classes share the same ObjectId ... ) Set the Multithreaded flag for this PersistenceManager . Applications that use multiple threads

otherwise. Multiple types can be specified if the implementation supports multiple types. Since: JDO 2.1

JDO Annotation Attribute in javax.jdo.annotations.Element Class[] types default {} Types of the elements. This can be determined if using JDK1.5 generics but is required otherwise. Multiple types can be specified if the implementation supports multiple types. Since: JDO 2.1

generics but is required otherwise. Multiple types can be specified if the implementation supports multiple

JDO Annotation Attribute in javax.jdo.annotations.Key Class[] types default {} Types of the keys. This can be determined if using JDK1.5 generics but is required otherwise. Multiple types can be specified if the implementation supports multiple types. Since: JDO 2.1

{} Column definition(s) for this member. Used for mapping multiple columns to the same member, for example relationships with multiple column foreign keys. Since: JDO 2.1 String customValueStrategy

JDO Annotation Attribute in javax.jdo.annotations.Persistent Column [] columns default {} Column definition(s) for this member. Used for mapping multiple columns to the same member, for example relationships with multiple column foreign keys. Since: JDO 2.1

. This can be determined if using JDK1.5 generics but is required otherwise. Multiple types can be specified if the implementation supports multiple types. Since: JDO 2.1 String unique default "" Whether the element column

JDO Annotation Attribute in javax.jdo.annotations.Value Class[] types default {} Types of the values. This can be determined if using JDK1.5 generics but is required otherwise. Multiple types can be specified if the implementation supports multiple types. Since: JDO 2.1

of the multiple fields identified by fieldNumbers. Parameters: fieldNumbers - the fields whose values are to be provided by multiple callbacks to the StateManager's providedXXXField method Since: JDO 1.0

of the multiple fields identified by number. Parameters: fieldNumbers - the fields whose values are to be replaced by multiple callbacks to the StateManager's replacingXXXField method Since: JDO 1.0