ObjectDB Database Search
151-200 of 200 resultsQuery fails with numerical values > 2^31 Hi ! I'm trying to execute the following query (from Java-code, also tried ObjectDB Explorer) delete from DataRecord p where p.TimeOfDeletion == 1410521635503 | |
ObjectDB version 2.2 has been released ObjectDB 2 . 2 has been released and it includes important additions and fixes: Added full support of JPA 2 Criteria Queries API ( issue #10 ) Added full support of JPA 2 Metamodel API ( issue #9 ... Doctor to handle additional issues. Improved query execution planner. Improved cleanup and reusing space | |
ObjectDB JPA 2.2 support ( java.util.stream.Stream | |
objectdb explorer in ver 2.2 and 1.0 that object explorer has lower functionality than in ver 2 . 2 eg garbarage collector or xml import ... You are right - some important features of ObjectDB 1.0 Explorer are not implemented yet in ObjectDB 2 . 2 . This is because ObjectDB 2 was written almost from scratch and the old Explorer does not match | |
Version 2.2.7 build 7/8 issue and my own method in query . This query "SELECT c FROM Customer c order by c.getNormalizedName()" returns List ... (a); a.setCustomer(c); em.persist(c); em.getTransaction().commit(); Query query = em.createQuery( "SELECT c FROM Customer c order by c.getNormalizedName()"); List resultList = query .getResultList | |
In version 2.5.2_05 does not work greatest by Date In earlier versions this query worked fine. In version 2 .5. 2 _05 does not work .orderBy(cb.desc(cb.greatest(root.get("createDate").as(Date.class)))).distinct(true) Thank you for your help. galandor Orlov Sergey Please try build 2 .5. 2 _06 that should fix this regression (of casting to Date ). support Support | |
Querys slower when execute a query after every persist The test case of the java file attachment persists many entities and executes a query after every persist. The execution time amounts 2 sec when the test persists 1000 entities. The execution time ... requires only 20 sec, but the test requires 100 sec. Why the querys will be more and more slower? In | |
jakarta.persistence.criteria.CommonAbstractCriteria (JPA) 2 .1 Public Instance Methods Set getParameters () Return the parameters of the query . Returns ... The CommonAbstractCriteria interface defines functionality that is common to both top-level criteria queries ... directly in query construction. Note that criteria queries and criteria update and delete operations | |
jakarta.persistence.Parameter of the parameter Type for query parameter objects. See Also: Query TypedQuery Since: Jakarta Persistence (JPA) 2 .0 Chapter 4 - JPA Queries (JPQL / Criteria) explains how to use Parameter . Public Instance ... must be assignable to this type. This method is required to be supported for criteria queries | |
Is ObjectDB better than competing object databases? do not support aggregate queries (max, min, count, sum and avg). ObjectDB supports rich queries , including aggregate queries , as part of its support of JPQL (JPA Query Language) and JDOQL (JDO Query Language). ObjectDB is faster than other products. | |
Updating JPA Entities and provide better support for automatic change tracking. UPDATE queries UPDATE queries provide an alternative way to update entities in the database. Using an UPDATE query is useful, especially when you must modify many entities in a single operation. The UPDATE Queries in JPA/JPQL section in Chapter 4 explains how to use JPA UPDATE queries . | |
jakarta.persistence.LockModeType refresh() ), or to Query .setLockMode or TypedQuery.setLockMode . Optimistic locks are specified using ... attempting to update the entity data. A lock with LockModeType.PESSIMISTIC_READ can be used to query ... with LockModeType.PESSIMISTIC_WRITE can be used when querying data and there is a high likelihood of deadlock or | |
jakarta.persistence.criteria.Expression: - the type of the expression Super Interfaces: Selection , TupleElement Type for query expressions. Since: Jakarta Persistence (JPA) 2 .0 The JPA Query Expressions (JPQL / Criteria) article explains ... (JPA) 3. 2 Predicate equalTo ( Expression value ) Create a predicate to test whether the expression | |
What are the main benefits of using ObjectDB? processes JPQL (JPA Query Language) and JDOQL (JDO Query Language) queries directly, where ORM tools first convert these queries to SQL and then transition the SQL to the DBMS for execution through a JDBC | |
JPA Shared (L2) Entity Cache several server-side caches: Cache of database file pages . Cache of query programs . Cache of query execution ... for a specific retrieval operation: // Before executing a query : query . setHint ("jakarta.persistence.cache | |
jakarta.persistence.NamedStoredProcedureQuery StoredProcedureParameter Since: Jakarta Persistence (JPA) 2 .1 Public Instance Methods QueryHint[] hints () Query ... sets is undefined. The hints element may be used to specify query properties and hints. Properties ... recognized by a provider must be ignored. All parameters of a named stored procedure query | |
jakarta.persistence.criteria.Predicate. Since: Jakarta Persistence (JPA) 2 .0 The Logical Operators in JPQL and Criteria API article explains ... Returns: a scalar expression of the given basic type. Since: Jakarta Persistence (JPA) 3. 2 Predicate ... testing for equality. Since: Jakarta Persistence (JPA) 3. 2 Predicate equalTo ( Object value ) Create | |
Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct), the inability to robustly query relationship fields in a web application renders the ObjectDB system seemingly useless. objectdb- 2 . 2 .5_10 NetbeansIDE6.9.1 Glassfish3.01 client-server mode. odb file ... showing the query result in indexTest.xhtml. The problems is illustrated by running the attached JavaEE | |
jakarta.persistence.criteria.CriteriaBuilder.In type. Since: Jakarta Persistence (JPA) 3. 2 Predicate equalTo ( Expression value ) Create a predicate ... Persistence (JPA) 3. 2 Predicate equalTo ( Object value ) Create a predicate to test whether the expression ... against Returns: predicate testing for equality. Since: Jakarta Persistence (JPA) 3. 2 String getAlias () Return | |
JPA Metamodel and Graphs, and their attributes to build dynamic queries and validate persistence structures. The Metamodel Access ... and further explanation, refer to the JPA Metamodel API section in the ObjectDB manual. Criteria query ... objects that can be bound to a Path in a Criteria query , mainly to define FROM variables | |
Deleting JPA Entities the database. DELETE Queries DELETE queries provide an alternative way to remove entities from the database. They are especially useful for deleting many entities in a single operation. For more information, see DELETE Queries in JPA/JPQL . | |
Posting Sample Code; em.getTransaction().commit(); Query query = em.createQuery("SELECT e FROM MyEntity e"); List resultList = query | |
JPA Optimistic and Pessimistic Locking query . Releasing a Pessimistic Lock Pessimistic locks are automatically released at the end ... mode can also be set for a query to lock all the query result objects. When a retrieval operation | |
ObjectDB 2.2.0 Added full support of JPA 2 Criteria Queries API ( issue #10 ) Added full support of JPA 2 ... ). Improved ObjectDB Doctor to handle additional issues. Improved query execution planner. Improved ... class. Fixed a query cache bug. Fixed several bugs in query processing and running. Fixed a query | |
JPA 2.2 LocalDate still not working Hello, I would have commented in this Thread but somehow I wasn't able to. Now again 2 years later ... ObjectDB version 2 .8.3 supports fields of types: LocalDate, LocalTime, LocalDateTime ... . Otherwise, on retrieval a Date instance may be instantiated. Currently selecting such a field in the query | |
ObjectDB 2.2.9) in queries . Added type information to enhancement exceptions. Improved support of non standard database file suffixes. Changed fetch of collection elements. Fixed a bug in query plans that use ... bug in complex JOIN queries . Fixed a NullPointerException in querying an empty database . Fixed | |
[ObjectDB 2.2.5_02] Unexpected exception (Error 990) com.objectdb.o.InternalException: java.lang.NullPointerException: null reporting issue as requested [ObjectDB 2 . 2 .5_02] Unexpected exception (Error 990) Generated ... { CriteriaQuery cq = em.getCriteriaBuilder().createQuery(); cq.select(cq.from(Chart.class)); Query q ... you for your report. Build 2 . 2 .5_09 should fix this NullPointerException . support Support Thank | |
ObjectDB 2.6.2 for NullPointerException on query after flush ( issue #1623 ). Improved title of query result ... in using EnumType.STRING based enum collection as a query parameter ( issue #1639 ). Fixed a synchronization bug ( issue #1643 ). Fixed a regression of build 2 .6.1_03 in supporting interfaces in | |
ObjectDB 2.2.3 evolution (regression of 2 . 2 .0). Fixed a bug in queries on large objects . Fixed a bug in using persistent properties with incomplete enhancement. ... Added support of @ElementCollection (for setting eager fetch of non entity collections, such as List ). Improved performance of eager fetch in queries . Added Maven build enhancement | |
ObjectDB 2.2.5 to the Server and Explorer About dialog boxes. Fixed an UPDATE/DELETE query bug in client-server ... of user defined serializable objects. Fixed a bug in using NOT NULL in criteria queries . Fixed a bug in using strings in criteria queries . Fixed a bug in collection change tracking in a new entity | |
ObjectDB 2.7.2 section key bug ( issue #2127 ). Fixed a bug in queries of the form "SELECT o FROM ... WHERE o == :arg ... file in place . Fixed a ClassCastException in query selection of embedded object and array fields. Fixed an InternalException on some JDO delete queries . Fixed a bug in processing a new index | |
ObjectDB 2.3.2 Fixed a bug in "p.id IN :ids" queries . Fixed a bug in handling NOT = queries ( issue #536 ). Fixed ClassCastException and NullPointerException in using a composite index in queries ( issue #531 ). Fixed Explorer bugs: editing embedded objects and using connection urls. Fixed | |
ObjectDB 2.4.2 by JOIN FETCH ( issue #854 ). Fixed type checking of query parameters. Changed merge implementation ... types. Fixed a bug of returning managed hollow objects in query results. Fixed an error message for invalid DELETE query ( issue #825 ). | |
ObjectDB 2.2.4 Added support of JPA UPDATE and DELETE queries ( issue #12 ). Added support of pessimistic lock timeout ( javax.persistence.lock.timeout ). Added implementation of the getParameters method. Added ... objects in criteria queries . Improved Explorer performance by disabling EAGER fetch. Fixed critical | |
ObjectDB 2.0.2 Fixed a bug in queries on embedded objects in C/S mode. Fixed a bug in setting log directory path (missing URL decoding). Fixed a bug in automatic byte code enhancement in Java EE server. Fixed a bug in multi variable queries . | |
ObjectDB 2.2.1 Added support for using ObjectDB with JBoss AS 6.0 / 6.1 . Fixed several bugs in handling eager fetch. Fixed a pessimistic locking bug . Fixed a bug in using primary key fields in queries . Fixed a bug in queries on deleted objects before commit / flush. | |
ObjectDB 2.2.8 Fixed a critical bug in extensive removal operations of large objects. Improved the performance of navigation through an inverse (mapped by) field if the owner field is indexed. Fixed a LEFT OUTER JOIN bug . Fixed a bug in parsing queries with parenthesis followed by NOT . Fixed a bug in running | |
ObjectDB 2.2.7 Added support of report generation using BIRT . Fixed a bug in query optimization of DISTINCT. Fixed a bug in keeping removed entity object in the L2 cache. Fixed orphan removal of owner entity object in bidirectional relationship. Fixed an "Attempt to persist a reference to a non managed instance | |
ObjectDB 2.5.2 of a composite BETWEEN query . Fixed NullPointerException when using AND TRUE in WHERE clause (issue | |
ObjectDB 2.2.6 ). Fixed an error message for invalid query parameter ( issue @320 ). Fixed pom.xml files in the Maven tutorials to use Java 1.5 / 1.6. | |
ObjectDB 2.8.2 Added support of deleting classes in the Explorer. Improved memory cleaning when entity objects with embeddable elements are detached. Improved handling query results that include managed hollow objects. Removed false alarms by the Doctor. Fixed a deadlock ( issue #2512 ) on closing | |
ObjectDB 2.9.2_02 Fixed issue #2954 - using IS NULL (or == null) on parameters in queries . | |
jakarta.persistence.criteria.Path. Since: Jakarta Persistence (JPA) 2 .0 The Paths and Types in JPQL and Criteria API article explains ... expression of the given basic type. Since: Jakarta Persistence (JPA) 3. 2 Predicate equalTo ... for equality. Since: Jakarta Persistence (JPA) 3. 2 Predicate equalTo ( Object value ) Create a predicate | |
jakarta.persistence.ColumnResult ConstructorResult annotation to map a column of the SELECT list of a SQL query . The name element references ... can be included in the query result by specifying this annotation in the metadata. Example: Query q = em ... name () (Required) The name of a column in the SELECT clause of a SQL query Since: Jakarta | |
jakarta.persistence.EntityResult the SELECT clause of a SQL query to an entity result. If this annotation is used, the SQL statement ... . Example: Query q = em.createNativeQuery( "SELECT o.id, o.quantity, o.item, " + "i.id, i.name, i ... specified in the SELECT list of the query to the properties or fields of the entity class | |
jakarta.persistence.TypedQueryReference: - an upper bound on the result type of the query A reference to a named query declared via the NamedQuery ... ) Since: Jakarta Persistence (JPA) 3. 2 Public Instance Methods Map getHints () A map keyed by hint name ... .0 String getName () The name of the query . Since: Jakarta Persistence (JPA) 1.0 Class getResultType | |
jakarta.persistence.Tuple the elements of a query result tuple. See Also: TupleElement Since: Jakarta Persistence (JPA) 2 .0 Public ... - if tuple element does not correspond to an element in the query result tuple. Since: Jakarta ... does not correspond to an element in the query result tuple or element cannot be assigned | |
Step 4: Create an ObjectDB Data Set Queries against the database are represented in BIRT as data sets. To create the data set: Open ... this tutorial contains Point entities. We will use a simple JPQL query that retrieves points with x value in ... and paste to enter the above query and click Finish . When the data set is created successfully | |
Step 1: Create a Maven Web Project.objectdb.com com.objectdb objectdb 2 .8.1 org.eclipse.persistence javax.persistence 2 .1.0 javax.transaction jta 1.1 javax.servlet servlet-api 2 .5 provided javax.servlet.jsp jsp-api 2 .1 provided org ... .springframework spring-orm 3.0.5.RELEASE aopalliance aopalliance 1.0 cglib cglib 2 . 2 org.aspectj aspectjweaver | |
Step 1: Create a Maven Web Project; com.objectdb objectdb 2 .8.1 org.eclipse.persistence javax.persistence 2 .1.0   ... ; javax.servlet servlet-api 2 .5 provided   |