ObjectDB ObjectDB

Internal Website Search

21-30 of 200 resultsRefresh

Cascading makeTransient

. I supposed that makeTransient() should work somehow cascading even for the fields of the Entity ... new). Cascading makeTransient may solve the issue, but may cause other problems (slower makeTransient

Cascading delete

Is there a configuration parameter to set this? dmoshal David Moshal You can set cascade delete using annotations (see also the Orphan Removal section). JDO defines similar annotations, and both JPA ... configuration. You cannot set global cascade delete since that will be too risky - you may delete the entire database. support Support

Cascade delete with unidirectional mapping

Suppose entity A is referenced from entity B, like (A -> * B) but not actually having that reference, instead only B has @ManyToOne relationship to A and A has none. Is there a way to cascade delete ... ? vachagan Vachagan Operations are cascaded using relationships, so if you have no relationship in

Selective merge/cascade of detatched entity

=FetchType.EAGER, cascade=CascadeType.All) private Map<Company, Collection<Integer>> companyTargets ... activity that is too slow. The problem is with the cascading merge operation that becomes too heavy

Puzzler: Not getting cascades on read from Spring context

I've determined that the database is correctly initialized, looking at it from the Object Explorer, I can run the code that loads the database in a Junit test and it's initializing the children objects correctly, but in the application running in Jetty with Spring, fetching is not cascading

Error during cascaded merge

= "unit", cascade = CascadeType.ALL, orphanRemoval = true, fetch = FetchType.EAGER)     @OrderBy

ObjectDB 2.6.9_06 (embedded): Cascading merge resulting in duplicate objects

This issue maybe related to issue #110 (http://www.objectdb.com/database/issue/110). Because that issue has been closed as "fixed", I am reporting this new issue. This is my class definition: @Entity public abstract class Person {     @OneToMany(fetch=FetchType.EAGER, cascade=CascadeType

Cascading (persist) with a mix of enhanced and not enhanced entities

Cascading (persist) with a mix of enhanced and not enhanced entities

Cascade.ALL with LAZY fetchtype does not clean up all references on remove

Hello, I have a tree of entity classes that reference others using Cascade.ALL in combination with FetchType.LAZY. If I now delete a root entity using EntityManager.remove all leaf nodes will not be deleted. This only applies to the leaf nodes. If I add an additional the behaviour changes

JPA Entity Fields

EntityWithFieldSettings { @Basic(optional=false) Integer field1; @OneToOne(cascade=CascadeType ... . Cascade and fetch settings are explained in chapter 3. A persistent field whose type is embeddable

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