ObjectDB Database Search

101-150 of 200 results

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 ... ( "SELECT c FROM Customer c order by c.getNormalizedName()"); List resultList = query.getResultList ... . Your code should work again with build 2 . 2 .7_09. support Support

ObjectDB JPA 2.2 support ( java.util.stream.Stream )

Hi , in my database i want to fetch resultlist as big chunks.JPA 2 . 2 has new feature named Stream ... objectdb for JPA 2 . 2 ?  eix128 Kadir BAŞOL We hope to support this feature soon ... , similarly to the way that JPA 2 . 2 streams work. To free memory, however you will have to clear

Failure after ObjectDB 2.4.5_07 upgrade from 2.4.4_06

in order to understand the problem. Please check the database with the ObjectDB Doctor. Check also if returning to 2 .4.4_06 solves the problem. If the problem can be reproduced by a test case

How the sort order (in queries) works for non english letters?

(we are Czech company). How the sort order works for international (for us 'czech') letters? Does the ordering respects the national requirements? Thank you for clarification ... dmarko David Marko ObjectDB uses the ordinal Java String lexicographical order , which is based on the order

order by string with numbers

Hi Anyone could help me I need to order a string  for example user1, user2, ..., user1000 I ...   The sql that works is ORDER BY CAST(SUBSTR(username FROM 4) AS UNSIGNED) ASC Using JPQL SELECT u FROM Users u ORDER BY SUBSTRING(u.username,4)*1 ASC If you have other alternative for JPA

Order in WHERE Clause affects behaviour on DATE/DATETIME columns

("query", "%myQuery%"); I don't get any error! The order of the WHERE clauses obviously makes

objectdb-2.6.9_02 (with "objectdb.temp.no-enhancement-crc-check") vs. generic classes with interfaces: detailed investigation

objectdb- 2 .6.9_02 (with "objectdb.temp.no-enhancement-crc-check" system property ... there are now obsolete): -  Issue #1924 - ObjectDB- 2 .6.9: Failed to commit transaction: Failed ... the system, just for Expert System cases). To make things simpler, this posting will examine only these 2 cases

ObjectDB 2 has been released and is now more affordable

for all 2 .x versions. Private priority support will be sold separately in order to make ObjectDB ... Today, after years of hard work, ObjectDB 2 .0 was released and is available for download. In addition, in order to make ObjectDB more affordable, the pricing model was changed: The prices

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 downloaded the objectdb- 2 .5.5_02, activated it with our licence, enhancing went ... - 2 .0 file conversion Exception in thread "main" java.lang.RuntimeException: Internal Exception

A few entities loss after update to 2.3.7_08!

The old database is created by 2 .3.6. And recreate the database by doctor is useless. But the other version such as 2 .3.7 works fine. So we believe 2 .3.7_08 has a bug. codefad FrankChu More details are required in order to understand the problem. support Support

Apache Tomee 1.5.2: Failed to use JTA (TransactionManager is not found)

Hello, ObjectDB team! I am struggling with getting ObjectDB 2 .5.0 to work with clean Apache Tomee 1.5. 2 with transaction-type="JTA". I don't have any configurations in Tomee (objectdb.jar is in ... a resource loading problem. ObjectDB cannot find TomEE's TransactionManager , which is required in order

JPA Level 2 Cache - app config

Hello! I would like to use selective cache for JPA Level 2 (cached in EntityManagerFactory) in ... #The_cache_element_  specifies only amount of MB used for Level 2 cache, but the config is at server level, yet I need it at application level . This is a "must need" in order to use ObjectDB

Help: After upgrading from 2.2.8_02 to 2.2.8_04, can't perform LIKE query

Hi,   AFter the upgrade from 2 . 2 .8_02 (not sure if it was build 03/04 as I skipped 03 ... =false) OR ($1.conditionThree=false)))) Exception in thread "main" [ObjectDB 2 . 2 .8_04] Unexpected ... The criteria query AND/OR fix in 2 . 2 .8_04 caused this new problem. Please try build  2 . 2 .8_05

Glassfish 3.1.2.1 and ObjectDB 2.4.3

- The requested resource () is not available. I tried it on Glassfish server 3.1. 2 and 3.1. 2 . 2 . Sometimes I ... INFO: Running GlassFish Version: GlassFish Server Open Source Edition 3.1. 2 (build 23) INFO: Grizzly ... : Created HTTP listener [http-listener- 2 ] on host/port [0.0.0.0:8181] INFO: WEB0169: Created HTTP

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

jakarta.persistence.AssociationOverride

that is being overridden in order to specify it as part of the map value. If the relationship ... { ... } Example 2 : Overriding the mapping for phoneNumbers defined in the ContactInfo class @Entity public class ... (JPA) 2 .1 JoinTable joinTable The join table that maps the relationship. The joinTable element

ObjectDB 2.2.2

Changed log format to include date and time . Changed class loader management. Fixed handling multiple order expressions in inverse (mapped by) fields. Fixed the behavior of CacheStoreMode setting in L2 shared cache. Fixed  TreeSet and TreeMap  element comparison bugs. Fixed an Explorer

Strings in JPQL and Criteria Queries

to 'aly' . SUBSTRING('Italy', 3, 2 ) is evaluated to 'al' . Positions are one-based (as in SQL), not ... ); Expression l2 = cb. locate (path, "x"); Expression l3 = cb. locate (path, param, cb. literal ( 2 )); Expression l4 = cb. locate (path, "x", 2 ); // LOWER(str) and UPPER(str) Expression lower = cb. lower (path

Numbers in JPQL and Criteria Queries

. For example: MOD(11, 3) evaluates to 2 . MOD(8, 4) evaluates to 0 . The MOD function takes two integer ... function returns the square root of a specified argument. For example: SQRT(9) is evaluated to 3 SQRT( 2 ... (+) Expression sum1 = cb. sum (path, param); // 2 expressions Expression sum2 = cb. sum (path, 1000

queries under 2.7.6_4 significantly slower than under 2.7.6

we update to the latest version from 2 .7.6. Now we have the problem that we have numerous logs ... since version 2 .7.6 that could possibly effect query execution. Could you please explain or post some of these logs that show deep query plan checks (and are new in 2 .7.6_04)? In addition

jakarta.persistence.AttributeOverride

order to specify it as part of the map key or map value. To override mappings at multiple levels ... ) { ... } } Example 2 : @Embeddable public class Address { protected String street; protected String city

queries more than 10 times slower using 2.8.1 versus 2.7.6

- we restarted to try to use 2 .8.1 instead of 2 .7.6 - we did a doctor on the database ... in 2 .7.6 around 5-10 seconds takes in 2 .8.1 around 150-200 seconds: SELECT DISTINCT o.parentNode ... .parentNode.classIdentifier = "(ME)" order by o.parentNode.modified desc     hgzwicker Hans

ObjectDB internal error on 2.6.5 for some query which worked on 2.6.4

Following query caused NULL pointer exception. Also this query worked fine on ObjectDb 2 .6.4b6 ... ="MESSAGE" OR $1.keyDescriptor.name="CONTEXT")) ORDER BY $1.timestamp 1. Priority HIGH since affected customers. 2 . Attached screenshot + database exampe Harman Alexander Golyshkin Thank you for this report

ObjectDB License

. You are encouraged to test ObjectDB before purchasing a license. Server License ObjectDB 2 .x Server License costs £500  and includes all version 2 .x updates. A server license covers one installation ... a Server License Site License ObjectDB 2 .x Site License costs £2,500  and includes all version 2 .x

Collation and String Order

will affect the way strings are sorted in queries (with ORDER BY). Currently strings are always ordered by Unicode order , and a workaround that enables controlling the order is to use normalizing, as ... feature. Many CRMs, DMS and other systems requires correct collation when using order by clause.  +1 for this ... dmarko David Marko

JPA Class Enhancer

line: ObjectDB Enhancer [version 2 .9.4] Copyright (c) 2025, ObjectDB Software. All rights reserved ... lists the classes that have been enhanced: [ObjectDB 2 .9.4] 3 persistable types have been enhanced: test.MyEntity1 test.MyEntity2 test.MyEmbeddable 2 NON persistable types have been enhanced: Main test

jakarta.persistence.criteria.CriteriaQuery.orderBy(List)

orderBy (    List o ) Specify the ordering expressions that are used to order the query results. Replaces the previous ordering expressions, if any. If no ordering expressions are specified, the previous ordering , if any, is simply removed, and results will be returned in no particular order

objectdb-2.6.9_06: Extended Persistence Context fails: 'Attempt to begin a new transaction when a transaction is active'

objectdb- 2 .6.9_06 NetBeans8.1+Glassfish4.1.1 Mac OS X Possibly related:  How to Use a SF ... .test.mini.ejb.ExtProjectBuilder ! Then Clean and Build (objectdb- 2 .6.9_06.jar is already included ...   All_ , not shown.) The following strategy used to work for objectdb- 2 .4.0_05 , but fails

2.9.x query issue with @Unique constraint

: (u.userName=:userName). [Step 2 ] Order the results of step 1 by: u. [Step 3] Use NULL as a result ... Query doesn't return results in versions 2 .9.x when there's a unique property in (where/and .. or ... for :userName parameter 2 .8.9 Query plan description ============================ [Step 1] Scan type

Literals in JPQL and Criteria Queries

, -127L, 0L, 07777L float : 3.14F, 0f, 1e2f, - 2 .f, 5.04e+17f double : 3.14, 0d, 1e2D, - 2 ., 5.04e+17 ... . literal (1); Expression i2 = cb. literal (Integer.ValueOf( 2 )); Expression d = cb. literal (3.4

jakarta.persistence.EntityManager.createStoredProcedureQuery(String,Class...)

must be specified in the order in which the result sets is returned by the stored procedure invocation ... exist (or if query execution will fail). Since: Jakarta Persistence (JPA) 2 .1

ObjectDB 2.0.0

in preserving order of @EmbeddedId fields. Fixed a NullPointerException during cache cleanup. Fixed a bug in database file converter (from ObjectDB 1.0 to 2 .0). Fixed a bug in handling duplicate

ObjectDB 2.6.6

in handling embedded objects in queries. Fixed a bug in ordering query result by an expression ... some types of collection and map queries in version 2 .6.5.

ObjectDB 2.8.4

). Added support for a new query hint for setting a preferred variable processing order ( issue #2379 )

version 2.4.5+ with GlassFish 3.1.2, errors when runs application. Version 2.4.4 worked but not 2.4.5 or later

All latest versions later 2 .4.5+ even 2 .4.5_05 doesn't work, it deployed but errors when running. But 2 .4.4 worked javax.ejb.EJBException at com.sun.ejb.containers.BaseContainer ... Luc Have you tried 2 .4.5 or 2 .4.5_03? Because 2 .4.5_03 fixes a GlassFish integration issue . support

jakarta.persistence.Query

that will be in effect during query execution. Since: Jakarta Persistence (JPA) 3. 2 CacheStoreMode ... . Since: Jakarta Persistence (JPA) 3. 2 int getFirstResult () The position of the first result the query object ... : position of the first result. Since: Jakarta Persistence (JPA) 2 .0 The Running JPA Queries article

jakarta.persistence.TypedQuery

. See Also: Query Parameter Since: Jakarta Persistence (JPA) 2 .0 Chapter 4 - JPA Queries (JPQL / Criteria ... effect during query execution. Inherited from Query Since: Jakarta Persistence (JPA) 3. 2 CacheStoreMode ... . Inherited from Query Since: Jakarta Persistence (JPA) 3. 2 int getFirstResult () The position of the first

Entity Management Settings

attribute specifies the size of the shared level- 2 cache that is managed by the EntityManagerFactory and shared by all its EntityManager instances. To disable the level- 2 cache, specify 0 or 0mb

jakarta.persistence.criteria.CriteriaBuilder.asc(Expression)

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CriteriaBuilder Order asc (    Expression expression ) Create an ordering by the ascending value of the expression. Parameters: expression - expression used to define the ordering Returns: ascending ordering corresponding to the expression. Since: Jakarta Persistence (JPA) 1.0

jakarta.persistence.criteria.CriteriaBuilder.desc(Expression)

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CriteriaBuilder Order desc (    Expression expression ) Create an ordering by the descending value of the expression. Parameters: expression - expression used to define the ordering Returns: descending ordering

jakarta.persistence.criteria.CriteriaQuery.getOrderList()

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CriteriaQuery List getOrderList() Return the ordering expressions in order of precedence. Returns empty list if no ordering ... of ordering expressions. Since: Jakarta Persistence (JPA) 1.0

jakarta.persistence.criteria.CriteriaQuery.select(Selection)

order = q.from( Order .class); q.select( order .get("shippingAddress").get("state")); CriteriaQuery q2 = cb.createQuery(Product.class); q2.select(q2.from( Order .class) .join("items") .join("product

jakarta.persistence.EntityManagerFactory

graph entityGraph - entity graph Since: Jakarta Persistence (JPA) 2 .1 void addNamedQuery ( String ... (JPA) 2 .1 R callInTransaction ( Function work ) Create a new application-managed EntityManager ... . 2 void close () Close the factory, releasing any resources that it holds. After a factory instance

ObjectDB 2.7.2_x Doctor Yields "Index Requires Rebuild" Always

Take a .odb created with ObjectDB 2 .7. 2 or later OR EARLIER.  Run ObjectDB 2 .7. 2 Doctor on it.  See indexing errors reported. Run ObjectDB 2 .7.1 on same .odb and you will not see indexing errors. Run ObjectDB 2 .7. 2 (or later or earlier) Doctor with repair and create repaired.odb. 

Compatibility Problems Upgrading from 2.6.9_04 to 2.7.6

Hi, We are preparing to upgrade our database servers and application dependencies from 2 .6.9_04 to 2 .7.6.  The desired path was to upgrade the database servers to 2 .7.6 first, followed by ... path? Thanks,  Clinton CAPdev CAP Dev the desired path was to upgrade the database servers to 2 .7

jakarta.persistence.OrderBy.value

_name] [ASC | DESC] If ASC or DESC is not specified, ASC (ascending order ) is assumed. If the ordering element is not specified, ordering by the primary key of the associated entity is assumed. Default: "" Since: Jakarta Persistence (JPA) 1.0

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  

Eclipse/JPA Java EE Tutorial

: ObjectDB 2 .3.7_04 or later is required if Glassfish 3.1. 2 (or later) is used. The Tutorial Steps This tutorial consists of the following steps:

NetBeans/JPA Java EE Tutorial

and menus might look slightly different but the code would be the same). Note: ObjectDB 2 .3.7_04 or later is required if Glassfish 3.1. 2 (or later) is used. The Tutorial Steps This tutorial consists of the following steps: