ObjectDB Database Search

. Then allow import of that file into another database. 2 . Lazy loading of data, especially in table view ... evaluation. For me, #1, # 2 and #3 would be the most important. Also, I've found some small bugs: 1 ... 'recent connections'. 2 . When editing a field in an @Embedded object, I get an error message

use a persistence.xml! The stacktrace looks like this: [ObjectDB 2 .3.6] javax.persistence ... .runners.ParentRunner$ 2 .evaluate(ParentRunner.java:222) at org.junit.internal.runners.statements ... ) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) at org.junit.runners.ParentRunner$ 2

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 ... .NameNotFoundException: Name [comp/TransactionManager] is not bound in this Context . Unable to find [comp]. at org

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

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

.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

Hello, the following exception appears when we execute a query:   [ObjectDB 2 .6.0_04 ... (InjectorImpl.java:229) at org.eclipse.e4.core. contexts .ContextInjectionFactory.invoke ... .renderers.swt.DirectContributionItem$ 2 .handleEvent(DirectContributionItem.java:331) at org.eclipse.swt

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

; JDOHelper.makeDirty . Fixed opening context menu in the Explorer.

: / by zero error on query execution. Fixed a bug in applying  OrderBy annotation. Fixed opening context menu in the Explorer.

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

context , resulting in, respectively, an insert or possible update when the persistence context ... to this persistence context , and has not been marked for removal, it is itself ignored, but the operation

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

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

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

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 (JPA) Method in jakarta.persistence.PersistenceContext PersistenceContextType type (Optional) Specifies whether a transaction-scoped persistence context or an extended persistence context is to be used. Default: PersistenceContextType.TRANSACTION Since: Jakarta Persistence (JPA) 1.0

to the current persistence context . Parameters: entity - entity instance Returns: boolean value indicating if entity belongs to the persistence context . Throws: IllegalArgumentException - if not an entity. Since: Jakarta Persistence (JPA) 1.0

the database when the persistence context is synchronized with the database, or make a removed entity ... is already managed, that is, if it already belongs to this persistence context , and has not been marked

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. 

are interpreted in the context of each entity class which inherits the mapped superclass

and the persistence context has been joined to it, will be marked for rollback. See Also: EntityManager

, if one is active and the persistence context has been joined to it, will be marked for rollback

, if one is active and if the persistence context has been joined to it, to be marked for rollback

Jakarta Persistence (JPA) Annotation Type jakarta.persistence.PersistenceContexts Implemented Interfaces: Annotation Target: Type Declares one or more PersistenceContext annotations. It is used to express a dependency on container-managed entity manager persistence contexts

referencing context ; not needed when dependency injection is used. Default: "" Since: Jakarta Persistence

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

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

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

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

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:

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

. 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