ObjectDB ObjectDB

Internal Website Search

1-10 of 200 resultsRefresh

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

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

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

Comparison in JPQL and Criteria API

== FALSE TRUE != TRUE FALSE Comparison operators are always evaluated to TRUE, FALSE or NULL. When both operands are not NULL (not shown in the table) the operator is evaluated to either TRUE or FALSE ... is true. All the other operators implement the SQL logic in which NULL represents an unknown value

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

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

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

[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

[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

[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

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