ObjectDB Database Search

1-50 of 200 results

Is ObjectDB better than Object Relational Mapping (ORM)?

As noted above, using ObjectDB instead of a relational database and ORM combination  ... of a relational database is mandatory (e.g. as a result of a customer request or when a new application is developed for an existing old relational database). By using the Java Persistence API (JPA

Can I use ObjectDB to access a relational database?

To access relational databases using the Java Persistence API (JPA) you will need an Object Relational Mapping (ORM) tool, such as Hibernate, TopLink, EclipseLink, Open JPA or DataNucleus. The DataNucleus ORM implementation supports also the Java Data Objects (JDO) API. ObjectDB is a full featured

Object Relations Error after Schema Change

Hi we have a problem with relations in OBjectDB 2.4.6, the problem occured after we changed relations in few clases. Specificaly we deleted relation pointing to one class and created new relation ... . Problem occurs when we create a new entry in the class we have changed the relation . Quote from

Entity is not related to ObjectDB, but i get exception from ObjectDB

, it is an exception from ObjectDB, although the entity itself is not related to ObjectDB any more. com

ObjectDB Explorer don't show ManyToOne relations

Hello support. we have a problem with the ObjectDB Explorer and @ManyToOne relations . We persist the entity FolderImpl that has an attribute of type ModelElement. If we use an interface for the attribute then the ObjectDB Explorer shows NULL for the attribute although our unit test checks

Speeding up the creation of Log entity objects related to other objects

In order to speed-up everything I would like to add log entities related to a device without touching (locking) the device entity. How can I do this with ObjectDB using @JoinColumn(name = "device") because I don't have a back reference from log to device! ----- @Entity public class Device

Error: Failed to write value of field X using reflection (oneToMany relation)

Error: Failed to write value of field X using reflection (oneToMany relation)

Eclipse Public License - v 1.0

. The obligations in this section do not apply to any claims or Losses relating to any actual or alleged ... to control, and cooperate with the Commercial Contributor in, the defense and any related settlement ... , or offers warranties related to Product X, those performance claims and warranties

Privacy Policy

 is any information that relates to an identified or identifiable individual. Service  refers ... of the Company, to perform services related to the Service or to assist the Company in analyzing ... an email and for other related website statistics (for example, recording the popularity of a certain

ObjectDB - JPA Object Database for Java

solution. Using a relational database management system (RDBMS) to store and retrieve Java objects requires slow conversions between graphs of Java objects and flat database table rows. Object Relational ... or NetBeans . Forget relational databases, JDBC, drivers, tables, records, ORM tools and mapping

What is the Java Persistence API (JPA)?

order to interact with a relational database such as Oracle, DB2, SQL Server or MySQL. The popular JPA ... . These implementations are Object Relational Mapping (ORM) tools. The mapping bridges between the data representation in the relational database (as tables and records) and the representation in the Java application

ObjectDB License Agreement [ver. 2.0.4]

out of or related to the use of or inability to use the Software, even if they have been advised ... out of, or related to, use of the Software. 6. The Customer may not disclose the results of any

Detached JPA Entities

to related entities, mark the reference field with CascadeType . DETACH or CascadeType ... the database. Cascading merge To automatically cascade a merge operation to related entities, mark

Is ObjectDB better than competing object databases?

relational database by using an ORM JPA provider such as Hibernate, EclipseLink or Open JPA ... is also unique in supporting features that are usually available only in relational databases. For example

jakarta.persistence.Graph

that include related managed types. Parameters: attribute - attribute Returns: subgraph for the element ... graphs that include related managed types. Parameters: attributeName - name of the attribute Returns ... for construction of multi-node entity graphs that include related managed types. Parameters

jakarta.persistence.EntityGraph

entity graphs that include related managed types. Inherited from Graph Parameters: attribute - attribute ... for construction of multi-node entity graphs that include related managed types. Inherited from Graph ... that include related managed types. Inherited from Graph Parameters: attributeName - name

FROM clause (JPQL / Criteria API)

define a join variable. Its only purpose is to specify related objects that should be fetched from

Auto Generated Values

. A minor difference relates to the initial value attribute. Whereas the SEQUENCE strategy maintains

JPA Query Structure (JPQL / Criteria)

The syntax of the Jakarta Persistence Query Language (JPQL) is similar to SQL. This is a key advantage because SQL is a powerful query language, and many developers are already familiar with it. The main difference between SQL and JPQL is that SQL operates on relational database tables, while JPQL

JPA Fetch Plan Graphs

for defining fetch plans of related entities or embeddables. It enables fine-grained control over deep

Retrieving JPA Entities

can trigger the automatic retrieval of related entities. By default, a retrieval operation cascades

JPA Named Queries

of named queries. However, because mapping files are mainly useful for Object- Relational Mapping (ORM

What are the main benefits of using ObjectDB?

fields can be stored by ObjectDB simply as part of the containing object. Relational databases lack

WHERE clause (JPQL / Criteria API)

JPQL expression syntax , which includes many operators (arithmetic, relational , and logical

SQL Queries Annotations

Jakarta Persistence (JPA) provides a set of annotations to define and map native SQL queries when the standard Java Persistence Query Language (JPQL) is insufficient. While ObjectDB focuses on JPQL and ignores these annotations, they remain essential for applications interacting with relational

Database Doctor

The ObjectDB Doctor tool provides two related services: Diagnose and validate an ObjectDB database file : Checks a specified ObjectDB database file to verify its integrity. If the file is corrupted, the tool produces a detailed diagnostic report that lists all errors. Repair a corrupted ObjectDB

What is ObjectDB?

relational database systems (RDBMS), such as Oracle, DB2, SQL Server or MySQL.

jakarta.persistence.EntityManager

it. This operation cascades to every entity related by an association marked cascade=DETACH . If the given entity ... identity. This operation cascades to every entity related by an association marked cascade=MERGE ... call to remove . This operation cascades to every entity related by an association marked cascade=PERSIST

jakarta.persistence.Converter

and must be annotated with the Converter annotation or declared as a converter in the object/ relational

jakarta.persistence.EntityManagerFactory

Jakarta Persistence (JPA) Interface jakarta.persistence.EntityManagerFactory Super Interfaces: AutoCloseable Interface used to interact with the persistence unit, and to create new instances of EntityManager . A persistence unit defines the set of all classes that are related or grouped by

jakarta.persistence.EntityResult

columns to related entities. The results obtained when insufficient data is available are undefined

jakarta.persistence.AttributeConverter

class must be annotated Converter or declared as a converter in the object/ relational mapping

jakarta.persistence.Graph.addSubgraph(String)

Jakarta Persistence (JPA) Method in jakarta.persistence.Graph Subgraph addSubgraph (    String attributeName ) Add a node to the graph that corresponds to a managed type. This allows for construction of multi-node entity graphs that include related managed types. Parameters

jakarta.persistence.Graph.addElementSubgraph(PluralAttribute)

related managed types. Parameters: attribute - attribute Returns: subgraph for the element attribute

jakarta.persistence.Graph.addTreatedElementSubgraph(PluralAttribute,Class)

entity graphs that include related managed types. Parameters: attribute - attribute Returns

jakarta.persistence.Graph.addSubgraph(Attribute)

Jakarta Persistence (JPA) Method in jakarta.persistence.Graph Subgraph addSubgraph (    Attribute attribute ) Add a node to the graph that corresponds to a managed type. This allows for construction of multi-node entity graphs that include related managed types. Parameters: attribute

jakarta.persistence.Graph.addKeySubgraph(Attribute)

Jakarta Persistence (JPA) Method in jakarta.persistence.Graph Subgraph addKeySubgraph (    Attribute attribute ) Add a node to the graph that corresponds to a map key that is a managed type. This allows for construction of multi-node entity graphs that include related managed types

jakarta.persistence.Graph.addKeySubgraph(Attribute,Class)

graphs that include related managed types. Subclass subgraphs will automatically include the specified

jakarta.persistence.Graph.addKeySubgraph(String)

Jakarta Persistence (JPA) Method in jakarta.persistence.Graph Subgraph addKeySubgraph (    String attributeName ) Add a node to the graph that corresponds to a map key that is a managed type. This allows for construction of multi-node entity graphs that include related managed types

jakarta.persistence.Graph.addKeySubgraph(String,Class)

graphs that include related managed types. Subclass subgraphs will include the specified attributes

jakarta.persistence.Graph.addElementSubgraph(String)

Jakarta Persistence (JPA) Method in jakarta.persistence.Graph Subgraph addElementSubgraph (    String attributeName ) Add a node to the graph that corresponds to a collection element that is a managed type. This allows for construction of multi-node entity graphs that include related

jakarta.persistence.Graph.addElementSubgraph(String,Class)

graphs that include related managed types. Parameters: attributeName - name of the attribute type

jakarta.persistence.Graph.addMapKeySubgraph(MapAttribute)

Jakarta Persistence (JPA) Method in jakarta.persistence.Graph Subgraph addMapKeySubgraph (    MapAttribute attribute ) Add a node to the graph that corresponds to a map key that is a managed type. This allows for construction of multi-node entity graphs that include related managed types

jakarta.persistence.Graph.addTreatedMapKeySubgraph(MapAttribute,Class)

-node entity graphs that include related managed types. Subclass subgraphs will automatically include

jakarta.persistence.EntityManager.refresh(Object)

Jakarta Persistence (JPA) Method in jakarta.persistence.EntityManager void refresh (    Object entity ) Refresh the state of the given managed entity instance from the database, overwriting unflushed changes made to the entity, if any. This operation cascades to every entity related by

jakarta.persistence.EntityManager.refresh(Object,Map)

made to the entity, if any. This operation cascades to every entity related by an association marked cascade

jakarta.persistence.EntityManager.refresh(Object,LockModeType)

the given lock mode . This operation cascades to every entity related by an association marked cascade

[ODB1] Chapter 6 - Persistent Objects

content, or a transient object, i.e. not related to any database. Storing Objects Explicitly ... , which represent database objects, and transient objects, which are ordinary memory objects not related to any

What is the Java Data Objects (JDO)?

), which is designated to be used with relational databases, JDO is designated to be used with both relational and object databases. JDO is supported by many object databases, including ObjectDB

[ODB1] Chapter 9 - ObjectDB Explorer

, because it is not related to a specific database. Section 9.4 explains how to work with threads in