ObjectDB ObjectDB

Internal Website Search

1-10 of 120 resultsRefresh

Auto Generated Values

strategies can be used as explained below. The Auto Strategy ObjectDB maintains a special global ... @GeneratedValue with the AUTO strategy: @Entity public class EntityWithAutoId1 { @Id @GeneratedValue(strategy=GenerationType.AUTO) long id; : } AUTO is the default strategy, so the following

"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: Exception in thread "main" [ObjectDB 2.3.2] javax.persistence.PersistenceException Unsupported auto value type java.lang ... (NetworkInformationDatabase.java:71) Caused by: com.objectdb.o.UserException: Unsupported auto value type java.lang.String

apache shardingsphere for auto sharding and replication possible ?

Hi , i have seen a project apache shardingsphere https://shardingsphere.apache.org/ You can look for detailed. It will be good if you add objectdb support for Apache ShardingSphere So we can use auto sharding and auto replication free... kadirbasol Kadir BASOL This is an interesting option that should be considered. Thanks. support Support

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 pawel Pawel Hryniszak


Enum Constant javax.persistence.GenerationType AUTO Indicates that the persistence provider should pick an appropriate strategy for the particular database. The AUTO generation strategy may expect a database resource to exist, or it may attempt to create one. A vendor may provide documentation


Enum Constant javax.persistence.FlushModeType AUTO (Default) Flushing to occur at query execution. Since: JPA 1.0


Enum Constantjavax.persistence.ValidationMode AUTO If a Bean Validation provider is present in the environment, the persistence provider must perform the automatic validation of entities. If no Bean Validation provider is present in the environment, no lifecycle event validation takes place. This is the default behavior. Since: JPA 2.0

Entity Management Settings

" /> <fetch hollow="true" /> <persist serialization="false" /> <cascade-persist always="auto ... > element <cascade-persist always="auto" on-persist="false" on-commit="true" /> The <cascade ... (whose value is "true", "false" or "auto") specifies if persist operations should always be cascaded

Setting and Tuning of JPA Queries

, which has two values: AUTO - changes are flushed before query execution and on commit/flush. COMMIT - changes are flushed only on explicit commit/flush. In most JPA implementations the default is AUTO. In ... query time flush at the EntityManager level: em.setFlushMode(FlushModeType.AUTO); // Enable

Feature suggestion: auto-detection of entities via persistence.xml extension

.autodetection" value="class, hbm"/> <property name="hibernate.hbm2ddl.auto" value="validate

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support