ObjectDB Database Search

Hi, I would like to update the ObjectDB from 1.0 to 2 .3.7_25. I used the License key ...   which i got after acting the 2 .0 odbee.jar. and any specific changes which i need to take care of when upgrading from 1.x to 2 .x. Thanks & regards, Binit Bhaskar binitbhaskar Binit Bhaskar

db odb file from version 1.x to 2 .x, user is unable to open the odb files in the application which is having object db 1.x installed. Is there any way to read odb files from 1.x in object db 2 .x ... binitbhaskar Binit Bhaskar Old ObjectDB 1.x databases cannot be opened directly by ObjectDB 2 .x

with our Eclipse update site, which was now fixed. A new version of the ObjectDB BIRT driver ( 2 .5.3) is now available, which requires ObjectDB 2 .5.3 or above (older versions can become available upon request). It should work with Eclipse 3.7, 4. 2 , and probably other versions. support Support

Hi, Is there any way to check, if 2 level cache is in use? Right now I've done two things: 1. objectdb.conf with cache size is placed in WEB-INF directory of my web application. 2 . persistence.xml ... by indexes without accessing the primary data. Currently this hint must be set at the query level

Using the current version of persistence.xml leads to an error: com.objectdb.jpa.Provider org.xml ... .     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

Hello :-). Are there any plans to support JPA 2 .1? I would wish to have a support for @AttributeConverter. Bot01 Frantisek Novak The general plan is to support future versions of JPA so probably JPA 2 .1 features will also be supported. support Support Thanks for the answer. And is there current

Is there any way to find out the number of current connections to the DB server? natmaclin Natalia Levine Currently not. You may subscribe to this feature request and update it according to your needs. support Support

Is there an API to get the current version of ObjectDB that's being used? This would be very handy to have, because it is somewhat difficult to know what version of the ObjectDB you are currently using since the objectdb.jar filename remains the same for all versions (which is not a bad thing by

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

- 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

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

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

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 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

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

.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

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 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

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

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

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

JPQL 2 .0 introduces the ability define FROM variables for map keys and values. Currently ObjectDB supports FROM variables for collection elements. FROM variables for map keys and values are expected ... both KEY and VALUE statements with JPQL with the latest version of ObjectDB 2 .3.7

(JPA) 1.0 void commit () Commit the current resource transaction, writing any unflushed changes ... whether the current resource transaction has been marked for rollback. Returns: boolean indicating ... (JPA) 3. 2 boolean isActive () Indicate whether a resource transaction is in progress. Returns

JPQL 2 .0 adds support of CASE statements for conditional expressions in queries, similarly to switch/case/default in Java, and based on the SQL syntax. Case statements are currently not supported by ObjectDB. support Support I wish to express also my interest in CASE statement support, which I

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

after the current transaction retrieved it, so the current transaction is attempting to modify a stale version ... that another user (using another EntityManager ) has modified the object since the current transaction ... (from another EntityManager instance) currently holds a PESSIMISTIC_WRITE lock on that database object

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

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

with the current transaction or whether the persistence context must be explicitly joined to the current transaction by means of the EntityManager.joinTransaction method. Since: Jakarta Persistence (JPA) 2 .1 Enum Constants SYNCHRONIZED Persistence context is automatically synchronized with the current

ObjectDB 2.2.2

only over the neighbors collection for the current c1 . In this case, propagating the WHERE constraint to the FROM ... _LENGTH, BOTH, BY, CASE, CHAR_LENGTH, CHARACTER_LENGTH, CLASS, COALESCE, CONCAT, COUNT, CURRENT _DATE, CURRENT _TIME, CURRENT _TIMESTAMP,DELETE, DESC, DISTINCT, ELSE, EMPTY, END, ENTRY, ESCAPE, EXISTS, FALSE

of the primary key column of the current table. Defaults to the same name as the primary key column ... with columnDefinition . Default: "" Since: Jakarta Persistence (JPA) 3. 2 ForeignKey foreignKey (Optional) Used ... (JPA) 2 .1 Additional JDK methods inherited from java.lang.annotation.Annotation java.lang.annotation

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. 

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

- 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

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

line as follows: $ java -jar explorer.jar If explorer.jar is not in the current directory ... the current database connection, use the File Close command. Viewing database content Viewer windows ... switches the current viewer to focus on that object. Executing queries The Query window on the left lets

whether the persistence context is always automatically synchronized with the current transaction or whether the persistence context must be explicitly joined to the current transaction by means of the EntityManager ... ) 2 .1 PersistenceProperty[] properties (Optional) Properties for the container or persistence provider

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

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

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

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 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

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

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

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

: 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:

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:

. 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

. It has a small footprint, high performance, and a flexible architecture (1-Tier, 2 -Tier or N-Tier). 1 ... developing software without a debugger. 1. 2   ObjectDB Operating Modes ObjectDB for Java/JDO