ObjectDB ObjectDB

Internal Website Search

51-60 of 200 resultsRefresh

Merge Issue: Attempt to reuse an existing primary key value

object share the same child on a ManyToMany relationship with Cascade.ALL constraint. public final ...         private String name;         @ManyToMany(cascade = {                 CascadeType ... ();     }     @Entity     static class A {         @OneToMany(cascade=CascadeType

How to Remove records from many to many relationship tables in JPA

TransportationEvent { ... @ManyToMany(fetch = FetchType.EAGER, cascade = CascadeType.PERSIST) private List ... { .... @ManyToMany( fetch = FetchType.LAZY, cascade = CascadeType.PERSIST) private List ... searching some forums i got syntax like @Cascade(org.hibernate.annotations.CascadeType.DELETE_ORPHAN

EntityManager JPA or JDO impl and different behavior

;         }                 @OneToMany(cascade=CascadeType.PERSIST, fetch=FetchType.EAGER)         public List ... ;             displayValues.put("en", name);         }         @OneToMany(cascade=CascadeType ... ://www.objectdb.com/api/java/jpa/OneToMany state: "When the collection is a java.util.Map, the cascade

Eclipse plugin problem (using ObjectDB as a separate bundle)

(unlike JDO) persist is not cascaded automatically to referenced objects by default ... - otherwise you get this exception. Alternatively, you can turn cascading persist on - including globally (as ... have NOT written one line of JPA code!! Setting all cascade-persist properties to true does NOT correct

Optimistic locking: prevent version increment on entity collection attribute

", cascade=CascadeType.PERSIST)     private List<Reading> readings = new ArrayList<Reading>(); The cascade mode is required in order to persist the Reading instances with the Document instance ... Support Ok, thank you for that. I have cascade persist set at the database configuration level

Mysterious "Attempt to persist a reference to a non managed instance" error

Serializable {     @Id @GeneratedValue private long id;     @OneToOne(fetch=EAGER, cascade=PERSIST) public Ostrich ostrich;     @ManyToMany(cascade=ALL) public Map<String, Index> entries ... that the cascading annotations would be sufficient to cause everything to be persisted (and that's worked

JPA vs JDO - which is more efficient for OneToMany queries?

field (again) or refresh it. 2) You have to persist both unless you have automatic cascade persist. In JDO all fields cascade persist operations automatically. In JPA you have to set it per field or ... one set automatic cascade globally? Seems useful for persist, delete, etc. dmoshal David Moshal


it is modified. Presumably that a blocking operation? Next question: how do I automatically cascade the refresh (ie for collections held by the object modified)? Can cascading refresh be set in the conf ... exceptions. Cascading refresh is set by annotations. support Support sorry for all the questions


Enum Constant javax.persistence.CascadeType ALL Cascade all operations Since: JPA 1.0


Annotation Element javax.persistence.OneToMany boolean orphanRemoval (Optional) Whether to apply the remove operation to entities that have been removed from the relationship and to cascade the remove operation to those entities. Default value: false Since: JPA 2.0

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