ObjectDB Database Search

51-100 of 200 results

Is persistence version 2.1 supported?

.     freddieFishCake Jonathan Lister Thank you for this report. Support of JPA 2 .1 format for persistence.xml  was added in build 2 .5.7_05. The url to java.sun.com doesn't exist, so the correct

ObjectDB version 2.1 has been released

ObjectDB 2 .1 has been released and it includes important additions and fixes: Added Online Backup utility ( issue #16 ). Added Master-Slave  Replication / Clustering (issue #17 ). Added a PDF ... of url arguments ( ";user=admin;password=admin" ). Changed default to NonTransactionalWrite enabled

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

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

javax.transaction-api-1.3.jar and javax.persistence-api.2.2.jar

has moved to jakarta.transaction-api and is now on version 2 .0.1 Questions: a) Do I need this library at all? b) If I do need it, do I use jakarta.transaction-api 1.3 or 2 .0.1? Similarly java.persistence-api. 2 . 2 .jar ships with the zip file, but this has also moved to jakarta, and is now

objectdb:2.8.4 & 2.6.1.b06 backward compatibility

We are decided to move our products from 2 .6.1.b06 to 2 .8.4, could you confirm that new objectDb 2 .8.4 is fully compatible with many already created databases based on 2 .6.1? So, it means that we need to be sure that new objectDb 2 .8.4 could read/write to databases created by 2 .6.1. Please confirm

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 ... the ObjectDB Doctor of version 2 . 2 in repair mode on existing database files, and to switch to the new

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

version 2.8.9_06 significantly slower for queries compared to 2.8.9

.objectdb.com/forum/2845 for queries we are using hgzpincher Hans-Georg Zwicker Version 2 .8.9_01 ... in version 2 .8.9_02 but maybe there is another relevant query performance regression that has not been fixed. Changes in versions 2 .8.9_03 - 2 .8.9_06 are not expected to affect queries. An attempt

Version 2.5.6 enhancement problem solved by updating to version 2.5.7_03

updated ObjectDB from 2 .5.6.x to 2 .5.7_03. Maybe this will save someone a bit of time and effort. - Ron AlphaOne Ron Brennan Actually build 2 .5.6 should also support Java 8 ... . But maybe build  2 .5.7_03 is somehow better for Java 8. Thanks for the report. support Support

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

GlassFish 3.1.2.2/JBoss 7.1.1

there are also issues with GlassFish 3.1. 2 (GlassFish 3.1.1 may work better with ObjectDB ... 2 .4.3 can be used with JBoss AS 7.1.1. As discussed in this forum thread - you will have to: Add ... ;directory). Add to the persistence.xml file a request to load the ObjectDB module. Build 2 .4.3 fixes

Version 2.2.7 build 7/8 issue

. Your code should work again with build 2 . 2 .7_09. support Support

Failure after ObjectDB 2.4.5_07 upgrade from 2.4.4_06

also if returning to 2 .4.4_06 solves the problem. If the problem can be reproduced by a test case

Memory Leaks after COMMIT operation (checked on versions 2.6.5 & 2.6.6.b01)

Memory Leaks after COMMIT operation (checked on versions 2.6.5 & 2.6.6.b01)

ObjectDB 2.3.0

Added the ability to edit databases in the Explorer ( issue # 2 ). Added the ability to execute queries in the Explorer (issue #3 ). Other small Explorer improvements. Added support of IN operator in JPQL queries. Added support of ";drop" database url parameter. Adjusted the Enhancer to the new

ObjectDB 2.5.1

) to-many relationship in embedded objects (issue #1131 , #13). Fixed a bug in automatic url

ObjectDB 2.1.1

Fixed an  Explorer bug in handling listeners and callbacks. Fixed a bug in using user/password url arguments multiple times. Fixed several bugs in query processing and running.

ObjectDB 2.1.0

exceptions . Added support of url arguments ( ";user=admin;password=admin" ). Changed default

ObjectDB 2.3.4

url . Fixed performance issue ( fetch optimization ) in range queries. Fixed cached result size

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

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

jakarta.persistence.StoredProcedureQuery

Since: Jakarta Persistence (JPA) 2 .1 Public Instance Methods boolean execute () Return true if the first ... . 2 CacheStoreMode getCacheStoreMode () The cache storage mode that will be in effect during query execution. Inherited from Query Since: Jakarta Persistence (JPA) 3. 2 int getFirstResult () The position

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

ObjectDB Object Database Features

Objects (JDO) Complete JDO 2 support (passed the JDO 2 TCK). Support for JDO 3 new features is in

jakarta.persistence.criteria.CriteriaBuilder

compatible with varags. Since: Jakarta Persistence (JPA) 2 .0 The JPA Criteria API Queries article ... more restriction predicates Returns: and predicate. Since: Jakarta Persistence (JPA) 3. 2 Expression ... . Since: Jakarta Persistence (JPA) 3. 2 Order asc ( Expression expression ) Create an ordering by

ObjectDB 2.2.2

ObjectDB 2.2.2

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

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

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

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 ... . It seems that running your query on your sample database with version 2 .8.1 is slower

Regression bug in using version 2.4.5 with GlassFish 3.1.2

Can't deploy objectDB ver 2 .4.5 or later using GlassFish 3.1. 2 , NetBeans 7. 2 .1 Win 7 & 8. ObjectDB Version 2 .4.4 is working good. [#|2012-12-18T05:26:53.167-0800|SEVERE|glassfish3.1. 2 |javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=44;_ThreadName=Thread- 2 ;|java.lang

[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 ... you for your report. Build 2 . 2 .5_09 should fix this NullPointerException . support Support Thank you for a quick turnaround. I can confirm it fixed using Build 2 . 2 .5_10 longpat Brian O'Hare

[ObjectDB 2.2.6_02] Unexpected exception (Error 990) at com.objectdb.o.OBC.aJ(OBC.java:961)

I was experiencing an exception so I did a test to reproduce it.   here it is. [ObjectDB 2 . 2 .6_02] Unexpected exception (Error 990) Generated by Java HotSpot(TM) Client VM 1.6.0_17 (on Windows ... O'Hare Thank you for your report and for the test. Please try build 2 . 2 .6_03 that should fix this exception. support Support

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 ... customers. 2 . Attached screenshot + database exampe Harman Alexander Golyshkin Thank you for this report. It seems to be related to the previous regression issue that you found. Build 2 .6.5_01 should fix it. support Support

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.

ObjectDB 2.2.0

Added full support of JPA 2 Criteria Queries API ( issue #10 ) Added full support of JPA 2 Metamodel API ( issue #9 ) Added non optional field validation (throwing an exception on null value). Improved ObjectDB Doctor to handle additional issues. Improved query execution planner. Improved

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 and objectdb still does not support LocalDate? com.objectdb.o._RollbackException: Failed to commit ... ObjectDB version 2 .8.3 supports fields of types: LocalDate, LocalTime, LocalDateTime

ObjectDB 2.9.2

3.x. JDO updated to API version 3. 2 .1 (API only, no new functionality). Note: JDO is not expected

ObjectDB 2.6.2

a synchronization bug ( issue #1643 ). Fixed a regression of build 2 .6.1_03 in supporting interfaces in

ObjectDB 2.2.8

ObjectDB 2.2.8

Report Generation with BIRT and JPA

= x :     (0, 0), (1, 1), ( 2 , 2 ), ..., (999, 999) The BIRT report

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:

[ODB1] Chapter 3 - Persistent Classes

). 3. 2   Persistent Fields and Types Storing a persistent object in the database does not ... of any of the persistent types defined above in the database (as demonstrated in section 2 .1 ... /*.class [ObjectDB Enhancer] 2 new persistence capable classes have been enhanced. [ObjectDB Enhancer] 1

[ODB1] Chapter 9 - ObjectDB Explorer

version to the same installation directory. 9. 2   Browsing the Database The ability ... viewer window (Table or Browser), as discussed in Section 9. 2 . Whether or not to use different

[ODB1] Chapter 4 - JDO Metadata

. Therefore, only the first metadata for a class in the search order specified above has effect. 4. 2    ... for determining if a field is persistent are explained in section 3. 2 . The persistence-modifier