ObjectDB ObjectDB

Internal Website Search

181-190 of 200 resultsRefresh
6

Optimistic lock failed

" /> <recovery enabled="false" sync="false" path="." max="100mb" /> <recording enabled="true" sync="false" path="." mode="write" />         <locking version-check="false
6

Object as parameter results in exception

misunderstood something again? Under eclipselink, this did work (going to PostgreSQL). If I change my path expressions to point to basic java types (path expression pointing to id):  @Override public T fetch
6

2.7.3_03 Erroneous "Attempt to modify a primary key of a managed object"

to display the actual letter case as entered by the user. My key is similar to a filing system path ... . When displaying the path, I can use the primary key to display the correct case, "My Drawer/MyFolder
6

JPQL JOIN FETCH Error

by a path with no variable (and maybe it is supported by Hibernate / HQL as an extension to JPQL ... get the error: Invalid fetch path: .titles for type ch.ethz.id.wai.doi.bo.Metadata John johnbrush John Brush
6

Failed to commit transaction: Attempt to commit a rollback only transaction

enabled="true" sync="false" path="." max="128mb" /> <recording enabled="false" sync="false" path
1

Strange Error with Criteria API and Sorting

, which is another variable. You can fix this specific query by using Path (which is not a separate variable) instead of Join: //final Join<?, ?> otherJoin = root.join("other"); final Path<Object> otherJoin = root.get("other"); support Support
1

ArrayIndexOutOfBounds with Critera API and function call

with CriteraBuilder.function("$1.getAge", Integer.class) ($1 is a valid path we've goot from our root ... .function("$1.getAge", Integer.class) ($1 is a valid path we've goot from our root selector) I
1

Best practise loading big data

about the number of instances in the heap per type and paths of strong references from roots to objects? support ... the configuration file that is actually used by ObjectDB. In recent releases of ObjectDB you can the path
1

ClassCastException in Tuple.get

.get chokes on Join, Root and probably other TupleElements that are not a Path - am I right? hobson ... with any TupleElement, be it Path, Join, Root, or whatever. It would make ObjectDB more conformant
1

Sort of very large objects - out of memory

" /> <recovery enabled="true" sync="false" path="." max="128mb" /> <recording enabled="false" sync="false" path="." mode="write" /> <locking version-check="true" /> <processing cache="8mb" max

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