ObjectDB ObjectDB

Internal Website Search

1-10 of 200 resultsRefresh

Lock prevents PersistenceManager.close when retainValues = false

to false. If retainValues == true, the code proceeds as expected. I don't understand ... for detachment during a PersistenceManager close operation. The retainValues == false mode affects commit


During the evaluation of ObjectDB (We're currently developing with EclipseLink/mysql) I noticed was the following: I marked a @Column as nullable=false Than I tried to save it with the property as ... (name="alarm_group_id", nullable=false) private AlarmGroup alarmGroup; bugsbunny2003 Marcel Rokers

recovery enabled="false", still creates tablename.odb$ files

Running in embedded mode, configuration specifies "<recovery enabled ="false"... />". Still, tablename.odb$ files get created, and if still present after an abrupt stop, the application will not restart properly. What do we need to do to not utilize recovery files (not have orphan tablename.odb

Logical Operators in JPQL and Criteria API

must be one of: TRUE, FALSE, and NULL. The following table shows how the AND operator is evaluated based on its two operands: TRUE FALSE NULL TRUE TRUE FALSE NULL FALSE FALSE FALSE FALSE NULL NULL FALSE NULL NULL represents unknown. Therefore, if one operand is NULL and the other operand is FALSE

Database Management Settings

enabled="true" sync="false" path="." max="128mb" /> <recording enabled="false" sync="false" path ... " synchronized="false" />   <index-update enabled="true" priority="40" /> <query-cache results ... for most applications. The <recovery> element <recovery enabled="true" sync="false" path="." max

Entity Management Settings

" /> <fetch hollow="true" /> <persist serialization="false" /> <cascade-persist always="auto" on-persist="false" on-commit="true" /> <dirty-tracking arrays="false" /> </entities ... specifies enhancement related settings: The agent attribute (whose value is "true" or "false

Literals in JPQL and Criteria Queries

including NULL, boolean literals (TRUE and FALSE), numeric literals (e.g. 100), string literals (e.g ... two boolean literals - TRUE and FALSE. Since JPQL is case insensitive, TRUE is equivalent to true and True, and FALSE is equivalent to false and False. Numeric Literals JPQL supports the Java syntax as

[ODB1] Chapter 5 - JDO Connections

.option.Optimistic", "false"); properties.setProperty( "javax.jdo.option.NontransactionalRead", "true"); properties.setProperty( "javax.jdo.option.NontransactionalWrite", "false ... ( "javax.jdo.option.RestoreValues", "false"); PersistenceManagerFactory pmf = JDOHelper

[ODB1] Chapter 6 - Persistent Objects

, false); The second argument of getObjectById(...) indicates whether or not the retrieved object ... = (Person)pm.getObjectById(oid, false); Notice that the newObjectIdInstance(...) method requires not ... [0]), s[1]); Person person = (Person)pm.getObjectById(oid, false); Retrieval by an Object Name

[ODB1] Chapter 4 - JDO Metadata

" /> <class name="D" requires-extent="false" /> </package> </jdo> A JDO metadata file ... , which includes the package name, has to be specified. requires-extent (true | false) By default, JDO ... -extent="false", as shown above for class D. If requires-extent="false" is specified for a class

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