ObjectDB ObjectDB

Internal Website Search

1-10 of 200 resultsRefresh
182

orphanRemoval = true not working when CascadeType.REMOVE is disabled

Dear all, I have entities Employee and Address, their relation is defined (full example in attachment): @Entity     public static class Employee { ....         @OneToMany(orphanRemoval = true)         private Set<Address> addresses; I'm expecting, that removing Employee from db, addresses
36

NPE using AND TRUE in WHERE clause

The following (dynamically generated) query causes an NPE: SELECT e FROM Event e WHERE e.account=:account AND TRUE When I change it to a trivial term which evaluates to true, it works fine: SELECT e FROM Event e WHERE e.account=:account AND 1=1 Here is the stack trace: om.objectdb.o
30

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 ... and the other operand is either TRUE or NULL, the result is NULL (unknown). ObjectDB supports the Java
23

Database Management Settings

enabled="true" sync="false" path="." max="128mb" /> <recording enabled="false" sync="false" path="." mode="write" /> <locking version-check="true" /> <processing cache="64mb" max-threads="10" synchronized="false" />   <index-update enabled="true" priority="40" /> <query-cache results
22

Entity Management Settings

: <entities> <enhancement agent="true" reflection="warning" /> <cache ref="weak" level2="0mb" /> <fetch hollow="true" /> <persist serialization="false" /> <cascade-persist always="auto" on-persist="false" on-commit="true" /> <dirty-tracking arrays="false" /> </entities
16

Collections in JPQL and Criteria Queries

IS EMPTY is TRUE if the collection is empty and FALSE otherwise. c.languages IS NOT EMPTY is FALSE if the collection is empty and TRUE otherwise. SIZE The SIZE(collection) function returns the number ... .languages is TRUE if languages contains 'English' and FALSE if not. 'English' NOT MEMBER OF c.languages
2

[ODB1] Chapter 4 - JDO Metadata

, which includes the package name, has to be specified. requires-extent (true | false) By default, JDO ... ="transactional" /> <field name="f3" default-fetch-group="true" /> <field name="f4" default-fetch-group="false" /> <field name="f5" embedded="true" /> <field name="f6
2

[ODB1] Chapter 5 - JDO Connections

", "true"); properties.setProperty( "javax.jdo.option.NontransactionalWrite", "false"); properties.setProperty( "javax.jdo.option.RetainValues", "true"); properties.setProperty ... class includes getter and setter methods: // Using the setter methods: pmf.setOptimistic(true
2

[ODB1] Chapter 6 - Persistent Objects

if its content in memory is up to date. If true is specified and the object in database is different ... should also be included (true indicates that subclasses are required). Iteration over an Extent is similar ... null). If obj is persistent, i.e. isPersistent(obj) returns true, the other methods provide
2

[ODB1] Chapter 7 - JDOQL Queries

the iterated object. Only instances for which the evaluation of the filter expression is true ... "", " ", "abcd\n1234", ... boolean true, false reference null As shown in the next section (section ... filter. It selects all the objects with the true value in that field. Other types of persistent fields

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