ObjectDB Database Search
51-100 of 200 resultsSpring Data JPA) ... 1 more If i understand the exception right Spring Data JPA calls getMetamodel on the entity ... Hello! When i configure Spring Data JPA to use ObjectDB 2.4.0_03 i get an exception ... .getMetamodel(Unknown Source) at org.springframework. data .jpa.repository.support | |
Spring Data JPA - PersistenceException thrown) at com.sun.proxy.$Proxy13.getMetamodel(Unknown Source) at org.springframework. data .jpa.repository ... ) at org.springframework. data .jpa.repository.config.JpaMetamodelMappingContextFactoryBean.createInstance(JpaMetamodelMappingContextFactoryBean.java:56) at org.springframework. data .jpa.repository | |
Wrong data stored in time only fields This may be related to the fix for the problem described in this thread: Wrong data stored in date ... are using the 2015g time zone data . While we cannot see a problem with date only fields (more testing ... and in 100K records it will show up in about 1 .5K records with no obvious pattern. Also it appears | |
Storing a tree of data (depth=3) of the data tree + 1 I'll explain it here: A movie is an entity (like the book) A movie has a list of roles ... @Entity and @Embeddable) and a roleName (String) There are other data like list of directors, list ... regards, Thomas APPENDIX : I'm using lombok ... @Entity @ Data @NoArgsConstructor | |
java.lang.ClassCastException in OSGi runtime when loading data from DB ClassCastExceptions on my "entity" classes when I try to read data from the DB. In a very old (2011?) forum ... . The entity obviously has to get loaded by all bundles in order to manipulate the data . This is the code ... ; TypedQuery typedQuery = entityManager.createQuery("SELECT FROM Person p WHERE p.id = 1 ", Person.class | |
Wrong data stored in date only fileds, for example 2am on the 25/10/2015 Madrid time (when clock goes back 1 hour at 3am), Object DB puts wrong data in the fields annotated with Temporal.DATE. The attached DB shows the problem ... the attached DB) to the DB: Record 1 : startDateTime = Sun Oct 25 02:00:25 CEST 2015 | |
Significant I/O costs during batch update or insert data. Our application has some complex entities. We do batch update(merge detached entity) every 2 minutes. We find the period significant IO costs these days, and disappeared when turn off the batch updating. 1 .ObjectDB is in embedded mode. 2.ObjectDB version is 2.3.7 3.Database file size is nearly | |
Unable to convert 1.x odb file to 2.x Hi, my company is just about to switch from ObjectDB 1 .04.2487 (SE) to ObjectDB 2. So I ... well, but then on converting 1 of the DB files I got this error: java -jar converter.jar ../old.odb ../new.odb ObjectDB 1 .0 ... . Output of conversion: ObjectDB 1 .0 - 2.0 file conversion | |
Query becomes slower on moving from ObjectDB 1.x to ObjectDB 2.x, with object 1 .x, the same query was getting executed within an seconds and now the same is taking around 40 ... logEntryIdList"); List param1 has the following data [5] List param2 , data is attached in the file as it was big query.execute(param1, param2); This takes 1 second to execute using objectdb1.x, but the same takes | |
GlassFish 3.1.2.2/JBoss 7.1.1). May be you have some ideas? When we just try JBoss 7. 1 . 1 nothing works at all. Where I can get a real ... . webel Dr Darren Kelly As discussed in a previous forum thread - JBoss 7. 1 . 1 is expected to be supported ... there are also issues with GlassFish 3. 1 .2 (GlassFish 3. 1 . 1 may work better with ObjectDB | |
jakarta.persistence.LockModeType attempting to update the entity data . A lock with LockModeType.PESSIMISTIC_READ can be used to query data using repeatable-read semantics without the need to reread the data at the end of the transaction to obtain a lock, and without blocking other transactions reading the data . A lock | |
jakarta.persistence.CacheRetrieveMode the database. Since: Jakarta Persistence (JPA) 1 .0 USE Read entity data from the cache ... , Comparable , Serializable Specifies how the EntityManager interacts with the second-level cache when data ... that data may be read from the second-level cache. BYPASS indicates that data may not be read from | |
Best practise loading big data is the main data provider within our solution. In the past we often discovered performance problems ... data access on a large 2 dimansional table. Internally we used a list entities which hold a list ... . Creating and traversing. For the traversing we access the data block by block - in each block step by | |
jakarta.persistence.AttributeConverter column. Since: Jakarta Persistence (JPA) 1 .0 X convertToEntityAttribute ( Y dbData ) Converts the data ... may be the same Java type. See Also: Converter Convert.converter Since: Jakarta Persistence (JPA) 1 .0 ... the entity attribute into the data representation to be stored in the database. Parameters: attribute | |
JPA Attributes Annotations Jakarta Persistence (JPA) annotations define how entity attributes (fields and properties) are managed. These annotations control data persistence behavior, including fetching strategies, relationship types, and data storage formats. General field mapping Configure standard state mapping behavior | |
ObjectDB - JPA Object Database for Java when the object data model is complex. See JPA benchmark results... Reduce development time. Improve ... Persistence API (JPA) Java Data Objects (JDO) Using a standard Java API (JPA / JDO) provides many benefits | |
JPA Runtime Tuning & Configuration to find() and lock() . Cache retrieve mode Controls whether data is read from the second-level cache: USE ... store mode Controls how data is stored in the cache: USE , BYPASS , or REFRESH . Scope Usage | |
JPA Criteria Queries: UPDATE and DELETE Queries CriteriaQuery is designed exclusively for data retrieval. Bulk data | |
Chapter 2 - JPA Entity Classes An entity class is a user-defined class whose instances can be stored in a database. To store data in an ObjectDB database using Jakarta Persistence (JPA), you define entity classes that represent your application's data object model. This chapter contains the following sections: | |
JPA Relationships Annotations how the persistence provider propagates operations and loads related data using these enumerations: Specifies ... whether related data is loaded immediately ( EAGER ) or on-demand ( LAZY ). Collection configuration Configure | |
JPA Annotations behavior. Declare static, reusable JPQL queries directly on the entity class. Optimize data retrieval by ... fields to persistent state, including primary keys, enumerated types, and temporal data . Define | |
JPA ORM Mapping Annotations for an entity, allowing data for a single entity to be split across multiple database tables ... within the hierarchy. An enumeration defining the data type of the discriminator column (STRING, CHAR | |
General Settings and Logging constraints, ObjectDB can use temporary files when processing large amounts of data , such as query ... . Therefore, ObjectDB uses temporary files only for data that exceeds a size limit specified by the threshold | |
jakarta.persistence.Cache. Since: Jakarta Persistence (JPA) 1 .0 void evict ( Class cls , Object primaryKey ) Remove the data ... Since: Jakarta Persistence (JPA) 1 .0 void evict ( Class cls ) Remove the data for entities of the specified ... cls , Object primaryKey ) Whether the cache contains data for the given entity. Parameters: cls | |
jakarta.persistence.SchemaManager creation , schema validation , data cleanup , and schema cleanup for entities belonging to a certain ... , otherwise, assume the schemas already exist Since: Jakarta Persistence (JPA) 1 .0 void drop ( boolean ... , drop schemas, otherwise, leave them be Since: Jakarta Persistence (JPA) 1 .0 void truncate () Truncate | |
each 1-2 days objects on some objectdb level lock/block each other each 1 -2 days we have the situation that our system changes to a completely underperforming mode ... % and around 200 threads hgzwicker Hans-Georg Zwicker According to the subject of this thread it happens every 1 -2 ... massive queries against the data rather than against the indexes. support Support Maybe setting  | |
JPQL Update & Delete (JPA 1.0) JPQL (Java Persistence Query Language) supports updating and deleting database objects by queries. Currently ObjectDB supports only JPQL SELECT (retrieval) queries. Delete queries are supported for JDOQL (JDO Query Language). support Support spring- data -jpa uses delete queries to implement | |
jakarta.persistence.criteria.CriteriaBuilder: absolute value. Since: Jakarta Persistence (JPA) 1 .0 Expression all ( Subquery subquery ) Create ... . Since: Jakarta Persistence (JPA) 1 .0 Predicate and ( Expression x , Expression y ) Create a conjunction ... : and predicate. Since: Jakarta Persistence (JPA) 1 .0 Predicate and ( Predicate... restrictions | |
jakarta.persistence.SecondaryTable one or more secondary tables indicates that the data for the entity class is stored across multiple ... , and have the same names and types as the referenced primary key columns of the primary table. Example 1 : Single ... (JPA) 1 .0 Annotation Elements String name (Required) The name of the table. Since: Jakarta | |
GROUP BY and HAVING clauses SUBSTRING(c.name, 1 , 1 ) FROM Country c GROUP BY SUBSTRING(c.name, 1 , 1 ); The FROM clause iterates ... : SELECT DISTINCT SUBSTRING(c.name, 1 , 1 ) FROM Country c GROUP BY with aggregate functions JPQL supports ... and the number of distinct currencies that those countries use: SELECT SUBSTRING(c.name, 1 , 1 ), COUNT(c), COUNT | |
Database Transaction Replayer of recording is data durability, you can keep the recording directory on a different physical device | |
Database Replication and Clustering root directory, $replication , which is located under the server's data root directory. To start | |
Is ObjectDB better than competing object databases? of the Java Data Objects (JDO) API than competing object databases. By using a standard API such as JPA | |
Index Definition is an ordered map data structure that ObjectDB maintains in the file system, not in memory. The B | |
JPA Query Structure (JPQL / Criteria) ...]] [ORDER BY ...] The SELECT and FROM clauses are required in every query that retrieves data ; update | |
JPA Extended API Reference Guide, criteria queries, and JPQL for data retrieval and manipulation. Describes the metamodel and graph APIs | |
DELETE Queries in JPA/JPQL an alternative way to delete entities. Unlike SELECT queries, which retrieve data from the database | |
What are the main benefits of using ObjectDB? multiple values (even for a simple data structure such as a collection of strings). In addition | |
JPA Core Types-level cache. Use it to check if specific entities are cached or to evict data to ensure | |
Database Doctor database file : Creates a new database file and copies all recoverable data from the corrupted file | |
What is ObjectDB? ObjectDB is an Object Oriented Database Management System (ODBMS). It provides all the standard database management services (storage and retrieval, transactions, lock management, query processing, etc.), but it uses an object oriented model to store and manage data . You can easily store ordinary | |
JPA Metamodel and Graphs The API supports the definition of fetch graphs to optimize data loading strategies at runtime | |
Database Schema Evolution these changes explicitly in the configuration to avoid data loss. The Schema Update section in Chapter 6 | |
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 | |
Running JPA Queries other cases, the expectation of a single result might be incorrect, depending on the data in the database | |
JPA Criteria Query Selection and Results The JPA Criteria API provides type-safe interfaces for defining query result expressions and ordering, mirroring the SELECT and ORDER BY clauses in JPQL or SQL. These interfaces allow you to specify exactly what data is returned and how it is sorted within the result set. SELECT clause elements | |
Step 3: Define a Spring DAO Component Operations on the database will be performed by an instance of a Data Access Object (DAO) that we will define in this step as a Spring MVC component: Open the [New Java Class] dialog box by right clicking the guest package node (in the [Projects] window under Source Packages) and selecting New | |
Step 3: Define a Spring DAO Component Operations on the database will be performed by an instance of a Data Access Object (DAO) that we will define in this step as a Spring MVC component: Open the [New Java Class] dialog box by right clicking the guest package node (in the [Package Explorer] window) and selecting New Class | |
Step 2: Create a Project and a Report file name (e.g. report.rptdesign ) and click Finish. The next step is creating an ObjectDB data source . | |
Which API should I use - JPA or JDO? You can use ObjectDB with either the Java Persistence API (JPA) or the Java Data Objects (JDO) API. Both share similar architecture, design and abilities. When to prefer JPA JPA is more commonly used. Therefore, it might be the first choice for most new applications. You can use JPA as |