ObjectDB Database Search

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

Hi, I notice that objectdb zip file has: javax.transaction-api- 1 .3.jar However that library 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

.sax.SAXParseException; lineNumber: 10; columnNumber: 135; cvc-elt. 1 : Cannot find the declaration ... .createEntityManagerFactory(Persistence.java:54) but reverting to version 1 .0 makes the error go away.     freddieFishCake Jonathan Lister Thank you for this report. Support of JPA 2. 1 format

You are right - some important features of ObjectDB 1 .0 Explorer are not implemented yet in ObjectDB 2.2 ... to the Explorer in future versions. Support of ObjectDB 1 .x is now limited, so new application should only use ObjectDB 2.x. Notice that ObjectDB 2.x also supports JDO better (JDO 2 instead of JDO 1 ). support Support

The FAQ states in the system requirements only that a JDK/JRE 1 .5 or 1 .6(prefered) is required. When I try to use the IBM JDK 1 .6.0 I get a GPF exception while creating the entity manager. Looks like a call to putInt on sun.misc.Unsafe object Does this mean there is a BUG in the IBM JDK or are not

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 ... application failed: C:\Users\Mircea\Documents\NetBeansProjects\natural7\target\natural7- 1 .0-SNAPSHOT

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

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 version of the ObjectDB manual (included in the download). Added sample (tutorials) Maven projects

ObjectDB enhanced classes fail when compiled to Java 1 .7 [ObjectDB 2.2.9_08 Enhancer] 28 persistable types have been enhanced: ... com.vaisala.jx.db.gdm.model.SourceType stack trace from jUnit test com.vaisala.jx.db.gdm.facade.BaseFacadeTest  Time elapsed: 0 sec 

(using Java SE 10.0. 1 ). So I tried to track down why it is not found via runtime and discovered

Hi  I have a db of around 1 .6 lakh records. But now am getting some unexpected error when accessing some of the entities. And when am fetching all the records using objectdb explorer its showing exception. I have diagnosis the db with objectdb doctor but not find any error. Please check

Regarding the  OEM license I've another issue: I've updated my macbook to the latest version of macos Sequioa 15.6. 1 (24G90). Unfortunately since then the mac-id behavior drives me crazy (*). If I create a new activation code for my objectdb.conf it will be valid sometimes for 2 hours

Will ObjectDB support JPA 2.1 CriteriaDelete?

Not Enhanced: ...: com.objectdb.o.TEX: Type ..._$$_javassist_1 is not found

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 ... . (PersistenceUnitLoader.java:120) at org.glassfish.persistence.jpa.JPADeployer$ 1 .visitPUD(JPADeployer.java:224

I have this error in log. The query can't return result. Thanks for help. LOG: [ObjectDB 2.5. 1 _05] Unexpected exception (Error 990) Generated by Java HotSpot(TM) Server VM 1 .7.0_55 (on Windows Server 2008 R2 6. 1 ). Please report this error on http://www.objectdb.com/database/issue/new com.objectdb

[ObjectDB 2.8. 1 ] Unexpected exception (Error 990) Generated by OpenJDK 64-Bit Server VM 1 .8.0_212 (on Linux 5.0.0-27-generic). Please report this error on http://www.objectdb.com/issue/new com ... .persist(EMImpl.java:415) at javax.persistence.EntityManager$persist$ 1 .call(Unknown Source) at org

In this code: String id = "my key"; ABC itemDb = pm.getObjectById(ABC.class, id); I get this: [ObjectDB 2.4. 1 ] Unexpected exception (Error 990) Generated by Java HotSpot(TM) Client VM 1 .6.0_29 (on Windows 7 6. 1 ). Please report this error on http://www.objectdb.com/database/issue/new com.objectdb.o

Subqueries (nested queries) have been added to JDOQL (JDO Query Language) in JDO 2. 1 . This is the main feature of JDO 2.0-2. 1 -2.2 that is not implemented yet in ObjectDB 2. support Support

2.7.2_01 suddenly some queries do only have 1 result even there are more results (you can use the database that you have from #308):   this query gives 1 result even there are a lot more: select o from ObjectNode o where o.classIdentifier = '(OP)' and o.state = 98 and o.type = 0 and o

Added support for using ObjectDB with JBoss AS 6.0 / 6. 1 . Fixed several bugs in handling eager fetch. Fixed a pessimistic locking bug . Fixed a bug in using primary key fields in queries. Fixed a bug in queries on deleted objects before commit / flush.

ObjectDB version 2.5.5 (and above) supports Java 8 (JDK 1 .8). Tracking changes to collections and maps using some new Java 8 methods is currently not fully supported. The main known issue is that orphan removal does not happen as a result of removing a reference to an object

Support Knowledge Base ObjectDB 1 .0 Manual Chapter 7 "JDOQL Queries" Section 7.2 "Query Filter Syntax" Subsection "Fields" Second to last sentence Remove "not" from that sentence.   "An attempt to access a field or invoke a method using a null reference results in a false evaluation

ObjectDB 2.5.1

JPQL Subqueries (JPA 1.0)

ObjectDB 2.9.1

ObjectDB 2.6.1

ObjectDB 2.3.1

ObjectDB 2.0.1

ObjectDB 2.8.1

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

ObjectDB 2.4.1

ObjectDB 2.7.1

ObjectDB 2.1.0

JPQL Update & Delete (JPA 1.0)

Integration with Java EE (JPA 1.0)

of the given name is not present in the managed type. Since: Jakarta Persistence (JPA) 1 .0 Set ... of the managed type. Since: Jakarta Persistence (JPA) 1 .0 Class getBindableJavaType () Return the Java ... . Since: Jakarta Persistence (JPA) 1 .0 BindableType getBindableType () Return the bindable type

of this PersistenceConfiguration class should use sharedCacheMode . Since: Jakarta Persistence (JPA) 1 .0 JDBC_DATASOURCE An instance of javax.sql.DataSource . Since: Jakarta Persistence (JPA) 1 .0 JDBC_DRIVER Fully qualified name of the JDBC driver class. Since: Jakarta Persistence (JPA) 1 .0 JDBC_PASSWORD Password for JDBC

Parameters: name - alias Returns: selection item. Since: Jakarta Persistence (JPA) 1 .0 Expression ... Persistence (JPA) 1 .0 Expression cast ( Class type ) Cast this expression to the specified type, returning ... of the containing query Returns: subquery root. Since: Jakarta Persistence (JPA) 1 .0 Join correlate ( Join

Persistence (JPA) 1 .0 Set getAttributes () Return the attributes of the managed type. Inherited from ManagedType Returns: attributes of the managed type. Since: Jakarta Persistence (JPA) 1 .0 ... . Since: Jakarta Persistence (JPA) 1 .0 CollectionAttribute getCollection ( String name ) Return

. Since: Jakarta Persistence (JPA) 1 .0 Set getAttributes () Return the attributes of the managed type. Inherited from ManagedType Returns: attributes of the managed type. Since: Jakarta Persistence (JPA) 1 .0 ... type. Since: Jakarta Persistence (JPA) 1 .0 CollectionAttribute getCollection ( String name ) Return

(); for (Object[] result : results) { System.out.println( "Country: " + result[0] + ", Capital: " + result[ 1 ... ) { System.out.println( "Country: " + result[0] + ", Capital: " + result[ 1 ]); } CriteriaBuilder.tuple ... ("Country: " + t.get(0) + ", Capital: " + t.get( 1 )); } The Tuple interface defines several other methods

. It takes a name, an initial value (default is 1 ), and an allocation size (default is 50). A sequence ... ="seq", initialValue = 1 , allocationSize =100) public class EntityWithSequenceId { // Use ... . This means that if you want sequence numbers to start with 1 when using the TABLE strategy, you must specify initialValue=0 in the @TableGenerator  annotation.

to connect to the server only from the specified IP addresses. For example, "127.0.0. 1 " (the local computer ... of "192.18.0.0-192.18.194.255,127.0.0. 1 " allows connections from any IP address in the range 192.18.0.0 - 192.18.194.255 and from 127.0.0. 1 . The admin attribute, with a value of true or false , specifies

a hash symbol ( # ), for example, Point# 1 . Specify a collection as a comma-separated list ... and primary key, separated by a hash symbol ( # ), for example, Point# 1 . Use Edit Set Reference Set to New ... the object by its type and primary key, separated by a hash symbol ( # ), for example, Point# 1 . Use Edit

StoredProcedureQuery EntityManagerFactory Since: Jakarta Persistence (JPA) 1 .0 The JPA Connections and Transactions ... . Since: Jakarta Persistence (JPA) 1 .0 void close () Close an application-managed entity manager ... : IllegalStateException - if the entity manager is container-managed. Since: Jakarta Persistence (JPA) 1 .0 boolean

the managed type. Since: Jakarta Persistence (JPA) 1 .0 Set getAttributes () Return the attributes of the managed type. Returns: attributes of the managed type. Since: Jakarta Persistence (JPA) 1 .0 ... Persistence (JPA) 1 .0 CollectionAttribute getCollection ( String name ) Return the Collection-valued

is not present in the managed type. Since: Jakarta Persistence (JPA) 1 .0 Set getAttributes () Return ... type. Since: Jakarta Persistence (JPA) 1 .0 CollectionAttribute getCollection ( String name , Class ... of the given name and type is not present in the managed type. Since: Jakarta Persistence (JPA) 1 .0

for Java EE Developers. GlassFish Server 3.0. 1 (or above). The last version of ObjectDB (just download and extract). The tutorial was written for Eclipse 3.6. 1 but it should work with other Eclipse versions ... : 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:

a specified order. 7. 1   Introduction to JDOQL A basic JDOQL query has the following ... . One of the useful string methods that is not supported by JDO 1 .0 but supported in ObjectDB ... : Calendar calendar = Calendar.getInstance(); calendar.clear(); calendar.set(2000, 0, 1 ); Date date