ObjectDB Database Search

Multiple Collection Fields not update correctly

multiple different applications access one odb file

Get multiple entities by Id

multiple LEFT JOINs do not work as expected

100% CPU when using multiple BETWEEN

Multiple @ID

Access to client/server database from multiple applications

Maven and multiple JARs

InternalError on multiple AND and JOIN Query

Using multiple databases

Query with FETCH JOIN returns multiple results instead of one.

Multiple joins did not return expected result

Issue with orphanRemoval and multiple EntityManagers

Multiple MEMBER OF query

one or more secondary tables indicates that the data for the entity class is stored across multiple ... { ... } Example 2: Single secondary table with multiple primary key columns. @Entity @Table(name

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

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. Default: "" Since: Jakarta Persistence (JPA) 1.0

to inherited fields or properties, and so the state of an entity instance might be stored across multiple table

Jakarta Persistence (JPA) Annotation Type jakarta.persistence.ManyToMany Implemented Interfaces: Annotation Target: Method, Field Specifies a many-valued association with many-to-many multiplicity , mapping to an intermediate table called the join table . Every many-to-many association

Jakarta Persistence (JPA) Annotation Type jakarta.persistence.ManyToOne Implemented Interfaces: Annotation Target: Method, Field Specifies a single-valued association to another entity class that has many-to-one multiplicity . It is not usually necessary to specify the target entity explicitly

Jakarta Persistence (JPA) Annotation Type jakarta.persistence.NamedNativeQueries Implemented Interfaces: Annotation Target: Type Declares multiple native SQL named queries. Query names are scoped to the persistence unit. The NamedNativeQueries annotation can be applied to an entity or mapped

Jakarta Persistence (JPA) Annotation Type jakarta.persistence.Converts Implemented Interfaces: Annotation Target: Method, Field, Type Used to group Convert annotations. Multiple converters must not be applied to the same basic attribute. See Also: Convert Since: Jakarta Persistence (JPA) 2.1

of multiple persistent fields or properties, across several entities, and so distinct instances

of embeddable type has nested mappings to multiple columns in one of the tables mapped by the entity

serially to begin and commit multiple transactions. Returns: EntityTransaction instance. Throws

order to specify it as part of the map key or map value. To override mappings at multiple levels

Jakarta Persistence (JPA) Annotation Type jakarta.persistence.AttributeOverrides Implemented Interfaces: Annotation Target: Type, Method, Field Used to override mappings of multiple properties or fields. Example: @Embedded @AttributeOverrides({ @AttributeOverride(name = "startDate", column

within the embeddable class. To override mappings at multiple levels of embedding, a dot ( . ) notation

when multiple converters would otherwise apply. Note that the target type X and the converted basic type Y

Jakarta Persistence (JPA) Annotation Type jakarta.persistence.AssociationOverrides Implemented Interfaces: Annotation Target: Type, Method, Field Used to override mappings of multiple relationship properties or fields. Example: @MappedSuperclass public class Employee { @Id protected Integer id

multiple problems might be reported, each as a separate exception instance. Since: Jakarta Persistence

back only via INOUT and OUT parameters as well as the most general case ( multiple result sets and/or update

. If there are multiple result sets, it is assumed that they are mapped using the same mechanism —

Jakarta Persistence (JPA) Annotation Type jakarta.persistence.NamedQueries Implemented Interfaces: Annotation Target: Type Declares multiple named Jakarta Persistence query language queries. Query names are scoped to the persistence unit. The NamedQueries annotation can be applied to an entity or

Jakarta Persistence (JPA) Annotation Type jakarta.persistence.NamedStoredProcedureQueries Implemented Interfaces: Annotation Target: Type Specifies multiple named stored procedure queries. Query names are scoped to the persistence unit. The NamedStoredProcedureQueries annotation can be applied

Jakarta Persistence (JPA) Annotation Type jakarta.persistence.OneToOne Implemented Interfaces: Annotation Target: Method, Field Specifies a single-valued association to another entity class that has one-to-one multiplicity . It is not usually necessary to specify the associated target entity

Jakarta Persistence (JPA) Annotation Type jakarta.persistence.OneToMany Implemented Interfaces: Annotation Target: Method, Field 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

. Since: Jakarta Persistence (JPA) 1.0 PersistenceConfiguration properties ( Map properties ) Set multiple

are still running? Another option, do you use multiple databases in that test? If you do, maybe ... to ObjectDB on each JVM? Maybe this issue is related to multiple threads, possibly using multiple databases, but on the same JVM rather than to multiple JVMs? support Support I checked it in

Hi there, Our app is highly scalable and can be distributed among multiple processes on multiple ... only limitation. Is there a way to spawn multiple server instances "embedded" into our app so we can avoid the single-process restriction though still have multiple processes to avoid a SPOF? Yes, the OEM

but only with an generel answer. What we need are multiple tenants (would be best if every tenant has its own file/db ... this with ObjectDB? ObjectDB doesn't support queries on multiple databases, so it is possible ... to open multiple databases, but currently we don't have an example that does that. If you use

Jakarta Persistence (JPA) Method in jakarta.persistence.PersistenceConfiguration PersistenceConfiguration properties (    Map properties ) Set multiple properties of this persistence unit. Parameters: properties - the properties Returns: this configuration. Since: Jakarta Persistence (JPA) 1.0

Jakarta Persistence (JPA) Method in jakarta.persistence.Graph 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

Jakarta Persistence (JPA) Method in jakarta.persistence.Graph Subgraph addTreatedSubgraph (    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

Jakarta Persistence (JPA) Method in jakarta.persistence.Graph 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

Jakarta Persistence (JPA) Method in jakarta.persistence.EntityManager EntityTransaction getTransaction() Return the resource-level EntityTransaction object. The EntityTransaction instance may be used serially to begin and commit multiple transactions. Returns: EntityTransaction instance. Throws

instance might be stored across multiple table rows. A join is used to retrieve the state of such entities. Since: Jakarta Persistence (JPA) 1.0

the remaining database objects, in which case multiple problems might be reported, each as a separate exception instance. Since: Jakarta Persistence (JPA) 1.0

Jakarta Persistence (JPA) Method in jakarta.persistence.Convert Class converter Specifies the converter to be applied. This element must be explicitly specified if multiple converters would otherwise apply. Default: jakarta.persistence.AttributeConverter/class Since: Jakarta Persistence (JPA) 1.0

you split the transaction to multiple smaller transactions? support Support     ... you split the transaction to multiple smaller transactions? Because it is a large transaction content ... can be larger than the database, since the same database page may be stored in the file multiple times