About auto

manual

Auto Generated Values

Explains the different strategies for generating auto values (mainly for primary key fields) in JPA.... page covers the following topics: The Auto Strategy The Identity Strategy The Sequence ... The Table Strategy The Auto Strategy ObjectDB maintains a special global number generator for ...

 
api-jpa

FlushModeType.AUTO

(Default) Flushing to occur at query execution.(Enum Constant of javax.persistence.FlushModeType)

 
forum_thread

"Unsupported auto value type java.lang.String" when persisting new instance

I don't have a simple test case for this issue, but I'm getting this error: ... 2.3.2] javax.persistence.PersistenceException Unsupported auto value type java.lang.String for field hr.hzmo.network.model.Device.ID ... by: com.objectdb.o.UserException: Unsupported auto value type java.lang.String for field hr.hzmo.network.model.Device.ID at ...

 
forum_thread

auto generate timestamp

Hi all, How can I create auto timestamping column? I want the database to generate the timestamp. I tried google but suggested solutions doesn't work in objectDB. http://stackoverflow.com/questions/811845/setting-a-jpa-timestamp-column-to-be-generated-by-the-database - Pawel   ... Hi all, How can I create auto timestamping column? I want the database to generate the ...

 
forum_thread

explorer feature request: ability to auto refresh

Request for feature: Ability to auto-refresh an explorer view, say at regular intervals of a few seconds. (at a minimum one ought to be able to manually refresh, for example the list of persistent types). additionally, it would be useful to be able to view an embedded database (read only mode) via the explorer.   ... Request for feature: Ability to auto-refresh an explorer view, say at regular intervals of a few seconds. ...

 
api-jpa

GenerationType.AUTO

Indicates that the persistence provider should pick an appropriate strategy for the particular database.(Enum Constant of javax.persistence.GenerationType)

 
api-jpa

ValidationMode.AUTO

If a Bean Validation provider is present in the environment, the persistence provider must perform the automatic validation of entities.(Enum Constant of javax.persistence.ValidationMode)

 
issue

Explorer bug ? Objects seem to be missing from database in Class view, but are present as references

objectdb-2.2.5_08 NetbeansID6.9.1+Glassfish3.01 I suspect the following is an Explorer bug. It is marked knowingly as CRITICAL by me because it makes the ObjectDB system unusable for a real project because it appears to be either database integrity corruption, or it just looks like it, which is just as bad. I attach a running project illustrating the problem, as well as screenshots. ... []: Created: com.greensoft.entity.Actor [null](TEST: auto actor 0) INFO: RequestBean []: Persisted: com.greensoft.entity.Actor [30](TEST: auto actor 0) INFO: RequestBean []: Created: com.greensoft.entity.Actor ...

 
forum_thread

Performance in large transactions

Hello, we have a performance problem when we use a large transaction. Let's do exactly the same in several transactions the ObjectDB works much faster. In our use case, we create many new entities and between the creations we call a select query. The execution of the query becomes slower at each iteration. (In the query, we search for an item of type Entity2. However, there is only one entity.)   Pseudocode for the fast and the slow solution FAST: ... setFlushMode ( FlushModeType . AUTO ) ; EntityTransaction transaction = ... setFlushMode ( FlushModeType . AUTO ) ; EntityTransaction transaction = entityManager. ... ; em. setFlushMode ( FlushModeType . AUTO ) ; em. getTransaction ( ) . begin ( ...

 
manual

Setting and Tuning of JPA Queries

Explains various JPA query settings - result range, flush and lock.... enum, which has two values: AUTO FlushModeType.AUTO enum constant (Default) Flushing to occur at query execution. ...