ObjectDB ObjectDB

Internal Website Search

121-130 of 168 resultsRefresh

Unable to update a OneToMany Set

the EntityManager after every operation your Company instance becomes detached. A detached entity object does not

Failed to write the value of field using reflection (error 363) on LAZY fetch

Please see this thread that also suggests a new setting ("objectdb.temp.no-detach") that may be useful for you. Regarding setting Spring Framework transactions in a way that JPA managed entities will not be detached

Error during cascaded merge

");     List<Unit> result = query.getResultList();     Unit unit = result.get(0);     em.detach ... ); } This is exactly what happens in our webapp. A unit entity gets detached, the user edits

JDO sequences from ORM file

$DetachablePersistenceCapable" detachable="true" />   <class name="JdoTypes$NonDetachablePersistenceCapable" detachable="false" />   <class name="JdoTypes$CacheableClass" cacheable="true" />   <class name="JdoTypes

"Attempt to lock a non entity object" error

the entire persistence context and detach all managed entity objects: ... Rolling ... expected and would prefer. AlphaOne Ron Brennan It is correct. All the entity objects are detached

problem with lazy loading - unittest project attached

object becomes detached. Since the relationship between Foo And Bar is lazy - it is unavailable in a detached Foo instance and the collection looks empty. support Support thanks for your help

Items in list are doubled, when the entity class is not enhanced

instance (which has never been detached). According to JPA - the merge operation is ignored for Customer ... check, so merge is called only on detached entities. If objectdb follows jpa, maybe we should ask jpa

Java 8 Enhancer Problem

. When I fetch, detach, change and merge an object I get the following exception: Caused by: com

ObjectDB 2.0.5

Fixed Java Agent / Java EE / Spring enhancement bug. Fixed a bug in merging detached entity objects. Fixed unexpected NullPointerException in client server mode. Fixed an exception in AVG query on non numeric values (issue #107). Fixed a bug in handling JOIN queries with primary key fields.

ObjectDB 2.3.7

Fixed a critical issue that may cause database corruption (issue #630). Initial attempt to enable navigation through lazy loading from detached objects (feature request #326). Improved toString of criteria queries to use aliases (issue #127). Fixed automatic variable naming in criteria queries

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