About auto

forum_thread

First query takes 4+ minutes to complete

Hi, we are evaluating ObjectDB 2.5.1_04 in embedded mode hoping to replace SQLite in our application. We observed that in our case it takes on average more than 4 minutes to complete the first SELECT query that we run on the DB which contains about 320,000 records of a single type of object. SQLite in comparison responds within few seconds on average with the same number of records. We hope to receive your recommendation on how to improve this result with this post.   Test System ... /> <cascade-persist always = "auto" on-persist = "false" on-commit = "true" /> ...

 
release

2.7.2

... ). Fixed a problem of EntityManager auto closing. Fixed ArrayIndexOutOfBounds on using a no arg ... Added new configuration to enable / disable auto serialization of non persistable types (now disabled by default). ...

 
forum_thread

Query results are not up to date for entities, not primitives

When using the CriteriaBuilder to query, the retrieved list are not refreshed according to the latest updates. But, when using the JPQL Query, the list are refreshed. What is the problem? ... / > <cascade - persist always = "auto" on - persist = "false" on - commit = "true" / ...

 
release

2.7.3

... ). Fixed a problem of EntityManager auto closing. Fixed ArrayIndexOutOfBounds on using a no arg ... Added new configuration to enable / disable auto serialization of non persistable types (now disabled by default). ...

 
release

2.7.1

... ). Fixed a problem of EntityManager auto closing. Fixed ArrayIndexOutOfBounds on using a no arg ... Added new configuration to enable / disable auto serialization of non persistable types (now disabled by default). ...

 
release

2.7.0

... ). Fixed a problem of EntityManager auto closing. Fixed ArrayIndexOutOfBounds on using a no arg ... Added new configuration to enable / disable auto serialization of non persistable types (now disabled by default). ...

 
issue

Unexpected Query Token / Casting in Query

Hi! Please find the attached database. Doing a simple query with casting SELECT COUNT(DISTINCT $1) FROM com.quasado.foundation.contact.individual.IndividualContact $1 WHERE UPPER(((com.quasado.foundation.warehouse.api.model.account.contact.IndividualContactDebitorAccountFragment) $1.qubletFRAGMENTMAP.get('com.quasado.foundation.warehouse.api.model.account.contact.IndividualContactDebitorAccountFragment')).debitorAccount.bankAccounts.routingNumber) LIKE UPPER('%28%') results in the error ... add another one anyway in our code because it is all auto-generated). Second thing: Can u easily extend odb to at least ... given case as well?   Our stuff is auto generated and cannot be changed as it is now nor replaced with manual code ...

 
release

2.6.9

... ). Fixed a problem of EntityManager auto closing. Fixed ArrayIndexOutOfBounds on using a no arg ... Added new configuration to enable / disable auto serialization of non persistable types (now disabled by default). ...

 
release

2.3.3

... Added new configuration to enable / disable auto serialization of non persistable types (now disabled by default). ...

 
release

2.6.8

... ). Fixed a problem of EntityManager auto closing. Fixed ArrayIndexOutOfBounds on using a no arg ... Added new configuration to enable / disable auto serialization of non persistable types (now disabled by default). ...