ObjectDB Database Search

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

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

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

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 (JPA) Method in jakarta.persistence.criteria.FetchParent Fetch fetch (    String attributeName ) Create a fetch join to the specified attribute using an inner join. Parameters: attributeName - name of the attribute for the target of the join Returns: the resulting

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.FetchParent Fetch fetch (    SingularAttribute attribute ) Create a fetch join to the specified single-valued attribute using an inner join. Parameters: attribute - target of the join Returns: the resulting fetch join. Since: Jakarta Persistence (JPA) 1.0

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.FetchParent Fetch fetch (    PluralAttribute attribute ) Create a fetch join to the specified collection-valued attribute using an inner join. Parameters: attribute - target of the join Returns: the resulting join. Since: Jakarta Persistence (JPA) 1.0

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.From Join join (    SingularAttribute attribute ) Create an inner join to the specified single-valued attribute. Parameters: attribute - target of the join Returns: the resulting join. Since: Jakarta Persistence (JPA) 1.0

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.From CollectionJoin join (    CollectionAttribute collection ) Create an inner join to the specified Collection -valued attribute. Parameters: collection - target of the join Returns: the resulting join. Since: Jakarta Persistence (JPA) 1.0

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.From Join join (    String attributeName ) Create an inner join to the specified attribute. Parameters: attributeName - name of the attribute for the target of the join Returns: the resulting join. Throws

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.From SetJoin join (    SetAttribute set ) Create an inner join to the specified Set -valued attribute. Parameters: set - target of the join Returns: the resulting join. Since: Jakarta Persistence (JPA) 1.0

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.From ListJoin join (    ListAttribute list ) Create an inner join to the specified List -valued attribute. Parameters: list - target of the join Returns: the resulting join. Since: Jakarta Persistence (JPA) 1.0

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.From MapJoin join (    MapAttribute map ) Create an inner join to the specified Map -valued attribute. Parameters: map - target of the join Returns: the resulting join. Since: Jakarta Persistence (JPA) 1.0

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.From CollectionJoin joinCollection (    String attributeName ) Create an inner join to the specified Collection -valued attribute. Parameters: attributeName - name of the attribute for the target of the join Returns

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.From SetJoin joinSet (    String attributeName ) Create an inner join to the specified Set -valued attribute. Parameters: attributeName - name of the attribute for the target of the join Returns: the resulting join. Throws

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.From ListJoin joinList (    String attributeName ) Create an inner join to the specified List -valued attribute. Parameters: attributeName - name of the attribute for the target of the join Returns: the resulting join

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.From MapJoin joinMap (    String attributeName ) Create an inner join to the specified Map -valued attribute. Parameters: attributeName - name of the attribute for the target of the join Returns: the resulting join. Throws

. 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

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

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

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

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

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.

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

mode are discussed in Section 1. 2 . Because the JDO API and the format of the database file ... is listening for new connections is specified in the configuration file (as explained in section 8. 2 ... to manage the server (stop, restart and start), and to exit the application. 8. 2   Single User

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

. 2   javax.jdo.PersistenceManager The javax.jdo.PersistenceManager interface represents ... retries (about 2 seconds) a JDOUserException (a subclass of JDOException ) is thrown. These constants

. 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