Fast Object Database for Java - with JPA/JDO support

Internal Website Search

11-20 of 200 resultsRefresh

Cascading persistence through an inverse field

Hi! I was playing with cascading persistence with @ManyToMany and inverse @ManyToMany fields, and I noticed that I can only get cascading persistence in one direction. If the "owner ... -related code to keep it simple. @Entity public class PointCollection { @ManyToMany(cascade

New entity objects are duplicated on merge cascading

When merge is cascaded to a new entity object that has not been persisted ... = GenerationType.AUTO)         private Long id;                 @OneToMany(cascade= CascadeType ... another new / dirty entity object by a reference with cascading persist disabled. The following test

I can't get cascading delete to work in JDO

I enclose a Netbeans project which demonstrates the problem. Cascading persist works, but cascading ... cascading delete has never been implemented in ObjectDB (see also "Deleting Dependent Objects" on this old documentation page). Build 2.7.5_04 implements cascading delete in JDO. Your NetBeans

Sometimes cascade persist does not work during commit

and the commit persists the entities B automatically by cascading. But sometimes the cascading doesn't ... ? // persist configuration: <cascade-persist always="auto" on-persist="true" on-commit="true" /> public ... int id; @Basic String strValue; @OneToMany (cascade

Cascading merge() leading to "Attempt to persist a reference to a non managed instance" error

with a parent/child relationship and cascading merge() operations. The parent has an application defined id ... (cascade = CascadeType.ALL)     @SuppressWarnings("unused")     private Parent owner;     public ... . Cascading merge to new entity objects (the Parent instances in your code) is currently broken

Memory leak while merging parent with No Cascade annotation with children

comparing Cascade.ALL (or Cascade.MERGE ) to nothing. Tested with last version of Object Db ( 2.5.5 ... MyEntity {         @Id         private String name;         @ManyToMany(cascade

Cascade type annotaion on an embeddable type

cascading is not required for the embedded objects themselves. There could be some specific case in which specifying Embedded is needed and it is related to cascading. If the embedded object contains a reference to an entity object with cascading annotation, it will be ignored by ObjectDB

Issue with cascade delete & add/remove

of Address which cascades deletes (orphanRemoval=true) to its children which is what we want ... Entities within the collection of a Contact when we delete the Contact? Is that cascaded or do we need ...     public static class Contact {         private String name = null;         @OneToMany(cascade

OneToMany and cascade delete problem

{ @OneToMany(targetEntity = Offer.class, mappedBy = "product", fetch = FetchType.LAZY, cascade = CascadeType ... . The problem is, that after removing product, all "connected" offers are also removed (cascade ... I think that the Offer class and cascading delete from Product

Selective merge/cascade of detatched entity

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

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