About null

issue

Use temporary files to enable very large transactions

We have transactions in which many objects are created. These objects are no longer needed in the current transaction after creation. Unfortunately, we will receive an OutOfMemory exception because the objects are kept in the first level cache of ObjectDB. In the forum thread http://www.objectdb.com/database/forum/921 on post #4 you wrote, that ObjectDB should support very large transactions in further version. Can you implement it that ObjectDB used temporary files? ... ) { if ( uid == null ) { return super . hashCode ... && this . getUid ( ) != null ) { return this . getUid ( ...

 
issue

Error on commit

I get the following on commit:  (v2.3.7_15) Let me know if you need more info. ... com.objectdb.o.InternalException: null com.objectdb.o.InternalException at ...

 
manual

JPA Persistable Types

Explains how JPA manages types, including entity classes, embeddable classes, primitive types, wrappers, string, date, enum, collections and maps.... and arrays and keys and values in maps) are either null values or instances of persistable types. In addition to ...

 
forum_thread

Schema Update: class hierarchy change

Hello, we try to change the class hierarchy of an Entity. You wrote www.objectdb.com/database/forum/899 that ObjectDB support automatic schema evolution for adding and removing fields and for class hierarchy change.   But our small test failed: At first create a DataBase with one Object of MyEntity ... of NamedEntity the field will be initialized as null . ObjectDB Support ObjectDB - Fast Object ...

 
forum_thread

JPA - ExceptionInInitializerError when creating EntityManager

EntityFactoryManager(emf) is successfully received but error at emf.createEntityManager Please see my code of fragment from my project. public class Main {        final private static Properties EMAIL_PROPS;      final private static String EMAIL_FROM;            static {  EntityManagerFactory emf = javax.persistence.Persistence.createEntityManagerFactory("tmpCLMSPU"); ... if (minutes != null && minutes instanceof String) ...

 
forum_thread

possible index required for improving query performance

Hi,   I have the following entity class:   @Entity @Table @Indices({ @Index(members={"relationshipType", "party"}), @Index(members={"relationshipType", "otherParty"}),     @Index(members={"relationshipType"}) }) @XmlRootElement public class Relationship implements Comparable<Relationship> { ... so I can't run this query in Explorer with a non-null parameter. If I run it with null, I can see in Explorer that it looks at the relationshipType index ...

 
issue

Error during closing an entity manager

Hello, can you explain the the following exception? Caused by: com.objectdb.o._PersistenceException: Failed to read the value of field field com.btc.ep.architecture.bl.internal.dmos.types.NormalizedAccessPathImpl.accessPathRoot using reflection at com.objectdb.o._PersistenceException.b(_PersistenceException.java:45) ~[na:na] at com.objectdb.o.JPE.g(JPE.java:145) ~[na:na] at com.objectdb.o.ERR.f(ERR.java:56) ~[na:na] at com.objectdb.o.OBC.onObjectDBError(OBC.java:1560) ~[na:na] at com.objectdb.o.OBM.close(OBM.java:212) ~[na:na] ... frames omitted Caused by: java.lang.NullPointerException: null at com.objectdb.o.OBC.az(OBC.java:468) ~[na:na] at ...

 
forum_thread

java.sql.Time field off by 30 minutes

Hihi, I'm wondering if this is a bug. I have a simple entity with java.sql.Time field. On writing and readback, the field is found to be 30 minutes off. It is observed on objectdb explorer as well. Timestamp works perfectly fine. Ps. dont think its a UTC issue. My system is set at far off UTC+30min time.   ... edit ...

 
issue

InternalException during producer/consumer scenario

Hi, I'm trying to use objectdb in a producer/consumer scenario. Producer threads put message objects into a table while consumer threads remove the objects based on age, priority, etc. There are 2 main motivations for using objectdb for this purpose rather than a queue or similar data structure: 1) The consumer can select the "next" object based on a range of potentially complex criteria. 2) The number of objects produced can be potentially exceed available memory so can be held on disk within the objectdb file. ... by the committed transaction. Passing null to EntityManager 's methods, such as remove , caused internal ...

 
issue

InternalException - error reading field from "queue" database

I trying to use an objectdb database as a persitent queue but have started getting the following error on the receiver side: ... following error: com.objectdb.o.InternalException: null com.objectdb.o.InternalException at com.objectdb.o.TYM.al(TYM.java:696) at ...