ObjectDB Database Search

51-100 of 200 results

Recommendation - concurrent access multiple class v

Hi! I've just started to architect a new system, stateless JSON API, which is expected to have very high load and to require more servers for parallel deployments (same app across multiple servers). I am considering using ObjectDB, because of its advantages and easy usage, but I'm afraid

Multiple inputs not supported on WHERE ?

); seems like objectdb doesnt support multiple where clauses ? "UPDATE LoginEntity u SET u.enabled = ?1

How can allow multiple null value in a Unique column.

, so indeed, for a unique field you cannot have more than one  null value. If you need multiple null values then 

Acces the same DB with multiple users

; not supporting multiple system prateek Prateek gupta

CriteriaQuery .where() for multiple conditions

CriteriaQuery .where() for multiple conditions

Multiple Collection Fields not update correctly

Multiple Collection Fields not update correctly

multiple different applications access one odb file

multiple different applications access one odb file

Get multiple entities by Id

Get multiple entities by Id

multiple LEFT JOINs do not work as expected

multiple LEFT JOINs do not work as expected

100% CPU when using multiple BETWEEN

100% CPU when using multiple BETWEEN

Multiple @ID

Multiple @ID

Access to client/server database from multiple applications

Access to client/server database from multiple applications

Maven and multiple JARs

Maven and multiple JARs

InternalError on multiple AND and JOIN Query

InternalError on multiple AND and JOIN Query

Using multiple databases

Using multiple databases

Query with FETCH JOIN returns multiple results instead of one.

Query with FETCH JOIN returns multiple results instead of one.

Multiple joins did not return expected result

Multiple joins did not return expected result

Issue with orphanRemoval and multiple EntityManagers

Issue with orphanRemoval and multiple EntityManagers

NullPointer running multiple client against server

Hi, I'm running objectdb in server mode, config as it comes out of the box. In this case the database is being used as a queue with multiple seperate processes, each with multiple threads, writing messages. The message is split into a lightweight metadata message to allow fast searching

Multiple MEMBER OF query

Multiple MEMBER OF query

jakarta.persistence.SecondaryTable

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

jakarta.persistence.NamedAttributeNode.keySubgraph

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

jakarta.persistence.NamedAttributeNode.subgraph

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

jakarta.persistence.InheritanceType

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

jakarta.persistence.ManyToMany

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.ManyToOne

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.NamedNativeQueries

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.Converts

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

jakarta.persistence.Embeddable

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

jakarta.persistence.Entity

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

jakarta.persistence.EntityManager

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

jakarta.persistence.AttributeOverride

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

jakarta.persistence.AttributeOverrides

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

jakarta.persistence.AssociationOverride

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

jakarta.persistence.AttributeConverter

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

jakarta.persistence.AssociationOverrides

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

jakarta.persistence.SchemaValidationException

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

jakarta.persistence.StoredProcedureQuery

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

jakarta.persistence.NamedStoredProcedureQuery

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

jakarta.persistence.NamedQueries

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.NamedStoredProcedureQueries

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.OneToOne

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.OneToMany

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

jakarta.persistence.PersistenceConfiguration

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

jakarta.persistence.PersistenceConfiguration.properties(Map)

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.Graph.addSubgraph(String,Class)

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.Graph.addTreatedSubgraph(Attribute,Class)

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.Graph.addSubgraph(Attribute,Class)

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.EntityManager.getTransaction()

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

jakarta.persistence.InheritanceType.JOINED

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