About ObjectDB

issue

NullPointer when accessing persistent field

I am afraid this is a large and complex example, and I do not encounter the problem in simple cases, therefore there is no example attached. I appreciate this may make the bug unreproduceable from your end.   ... bug unreproduceable from your end.   [ObjectDB 2.3.2] Unexpected exception (Error 990)   Generated by Java ... Server 2008 6.0). Please report this error on http://www.objectdb.com/database/issue/new com.objectdb.o.InternalException: java.lang.NullPointerException: ...

 
manual

Running JPA Queries

Explains how to use JPA to run Java Persistence Query Language (JPQL) queries. The Query javax.persistence.Query JPA interface Interface used to control query execution. See JavaDoc Reference Page... interface defines two methods for running SELECT queries: Query.getSingleRes ...

 
issue

Problem with JOIN and inheritance

Hello, Please run this query on the attached DB: SELECT DISTINCT $1 FROM com.quasado.serviceplaza.customer.VendorCustomer $1 JOIN $1.qubletFRAGMENTMAP $2, com.quasado.foundation.warehouse.contract.customer.CustomerContractsFragment $3 WHERE ((NOT (($2=$3) AND ($3.contracts IS EMPTY)))) The problem is quite easy: The "VendorCustomer" class inherits from the "Customer" class. ... posting instructions - before posting to the ObjectDB website. You may have to ...

 
issue

Support Attribute Conversion for Persistence

The @Converter annotation and the Attribute Converter interface have two big benefits: 1) They make it possible to persist as-yet-unsupported java types (in the example below, Period - part of the 1.8 java.time package. (It could just have well shown conversion to and from SQL Timestamp objects.  2) They also make it possible to persist custom objects that are fundamental to your domain in an efficient manner.  ... serialization="true" /> option in the objectdb.conf file).  2) They also make it possible to persist ... posting instructions - before posting to the ObjectDB website. You may have to ...

 
issue

Post-compile enhancement sometimes causes error in generic loops: incompatible types found: java.lang.Object: required: Entity

I have moved from automatic run-time enhancement to explicit post-compile enhancement in an Ant build.xml in a NetBeans web app, and sometimes on editing a file that performs a generic loops over and @entity type I get a generics error. The loop is:  for (Steel s: this.steelMaterials.getL_Steel().getEls()) { eSteelTableItems.add(asXmlElement(s)); } Where getEls() here gives: List<Steel> This sometimes (only, I don't understand the circumstances) gives this error: ... that demonstrates this issue? ObjectDB Support ObjectDB - Fast Object Database for Java (JPA/JDO) ...

 
forum_thread

Listing large number of complicated objects with paging.

Hi, For last few hours I was working on a problem with bad performance and memory problems with such a simple query: select prod from Product prod order by prod.id ASC Right now I have 55541 'Product' (attached to this post) entities in database and I'm trying to speed listing them with paging. The problem is, that running code that looks like this: ... is currently inefficient and has to be improved in future ObjectDB versions. Could you please provide more details about the ... you need in the SELECT clause. ObjectDB Support ObjectDB - Fast Object Database for Java (JPA/JDO) ...

 
manual

GROUP BY and HAVING clauses

Explains how to use the GROUP BY and HAVING clauses in a JPA/JPQL query.... clause which returns the first letters as result. ObjectDB is very flexible in allowing JPQL expressions anywhere in the ... BY clause is like the WHERE clause for the FROM clause. ObjectDB supports the HAVING clause only when a GROUP BY clause exists. ...

 
manual

JPA Query Structure (JPQL / Criteria)

Explains the structure of a JPQL query, which consists of 6 clauses: SELECT, FROM, WHERE, GROUP BY, HAVING, ORDER BY. The syntax of the Java Persistence Query Language (JPQL) is very similar to the syntax of SQL. Having a SQL like syntax in JPA queries is an important advantage because SQL is a very powerful query language and many developers are already familiar wi ...

 
issue

InternalException using 2.3.7_12

Sorry can't shed any light on this, other than the code where this came out of, worked fine with 2.3.7_02. I had to upgrade to 2.3.7_12 to pickup the fix for wildcard search on index, and now get this. [ObjectDB 2.3.7_12] Unexpected exception (Error 990)   Generated by Java HotSpot(TM) 64-Bit Server VM 1.6.0_21 (on Linux 3.0.0-16-generic). Please report this error on http://www.objectdb.com/database/issue/new com.objectdb.o.InternalException: java.lang.NullPointerException: null java.lang.NullPointerException... fix for wildcard search on index, and now get this. [ObjectDB 2.3.7_12] Unexpected exception (Error 990) Generated by Java ... 3.0.0-16-generic). Please report this error on http://www.objectdb.com/database/issue/new com.objectdb.o.InternalException: java.lang.NullPointerException: ...

 
issue

JQL-Update Queries fails with activated L2-Cache

When using JQL-Update Queries it is basically not working without calling entityManager.clear() after a transaction commit. When the clear() method isn't called the entityManager will never return a container the updated Entities. Scenario 1: Disabled L2 Cache, updating elements using UPDATE-Query and fetching Entities afterwards from database. Expected result: Getting changed Entities from database - Actual result: No changes are visble. ... Main entry point of sample application objectdb.conf edit ... clear the L2 cache explicitly. ObjectDB Support ObjectDB - Fast Object Database for Java (JPA/JDO) ...