ObjectDB Database Search
51-100 of 163 resultsEntityManager JPA or JDO impl and different behavior; @ OneToMany (cascade=CascadeType.PERSIST, fetch=FetchType.EAGER)   ... ; } @ OneToMany (cascade=CascadeType ... only at the database id. Second issue. The docs at: http://www.objectdb.com/api/java/jpa/ OneToMany state | |
Missing (null) elements in eager loaded references has a OneToMany relationship to DataElement. Every relationship is eagerly fetched Problem ... extends BaseCostElement { @ OneToMany (mappedBy = "parent" , fetch = FetchType. EAGER ) private List ... extends BaseCostElement { @ OneToMany (mappedBy = "parent" , fetch = FetchType. EAGER ) private List | |
Does ObjectDB support lazy loading? a Parent class which contains List , marked with @ OneToMany . After persisting a Parent object, (in ... to @ OneToMany (fetch=FetchType.EAGER), the properties can be read. It seems to me that ObjectDB doesn't ... A { @Id @GeneratedValue Long id; @ OneToMany (fetch=FetchType.LAZY, cascade=CascadeType.ALL) List list | |
can't get HashMap out of the database annotating the map with @ OneToMany (fetch=FetchType.EAGER). Outside the DAO method only fields ... signingDate; @ OneToMany (fetch=FetchType.EAGER, cascade=CascadeType ... class GuestHolder { // Persistent Fields: @Id @GeneratedValue Long id; @ OneToMany (fetch=FetchType | |
Merge Issue: Attempt to reuse an existing primary key value class A { @ OneToMany (cascade=CascadeType.ALL)   ... ; static class A { //@ OneToMany (fetch = FetchType.LAZY, cascade = CascadeType.ALL, mappedBy = "parent") @ OneToMany (fetch | |
mappedBy problem If I put the mappedBy element to the @ OneToMany , the owned side (the many side) will never persist ! for example @Entity public class Employee { @Id @GeneratedValue(strategy = GenerationType.IDENTITY) public Long id; public String name; @ OneToMany (targetEntity=Address.class,mappedBy="employee | |
Is it ok to put list or map of embeddable objects in entity ? Serializable { (...) @ OneToMany (cascade = CascadeType.ALL) List entityCList; } Where EntityC is some ... ;@ OneToMany (cascade = CascadeType.ALL) List embeddableBList; } It is not | |
problem with lazy loading - unittest project attached hi, i'm still testing objectdb together with spring-data-jpa. i made a test which should simulate 4 requests 1. save entity 2. read an existing entity, add onetomany relation 3. read an existing entity, add another onetomany relation 4. read entity, get relations. i have the feeling this is not | |
Removing an entity throws exception; optional=false, orphanRemoval=true) private Address address; @ OneToMany (mappedBy = "customer", fetch= FetchType.LAZY) private List itemList; @ OneToMany (mappedBy = "customer | |
Cannot sort descending, when ordering by caluculated float in a method { @ OneToMany (cascade=CascadeType.PERSIST)   ... , to demonstrate the issue: @Entity public class Invoice { @ OneToMany (mappedBy = "invoice", fetch | |
LEFT (OUTER) JOIN problem when mappedBy is defined invoices without items! Only invoices with items. When I remove mappedBy from @ OneToMany annotation ... public class Invoice { @ OneToMany (mappedBy = "invoice", fetch= FetchType.EAGER, orphanRemoval=true | |
Object explorer cannot open odb file. ObjectDB many-to-many relationship String code; @ OneToMany (mappedBy = "user") @MapKey private Map ... code; @ OneToMany (mappedBy = "project") @MapKey   | |
Apparent Lazy Loading issues./ OneToMany state: "When the collection is a java.util.Map, the cascade element and the orphanRemoval ... .ALL on a OneToMany map, then the cascade ONLY applies to the values, NOT to the key. This means all keys | |
LAZY @ManyToOne field functions as EAGER an unmapped @ OneToMany list is not still viewable, although a mapped @ OneToMany list is, which I | |
Persisting collection where members are subclasses OK, I have a number of classes which are all subclasses of Entry (e.g., Folder, Link, Book). In the Folder class, there is a @ OneToMany Map children If I store something in that map ... ; @ OneToMany (cascade=CascadeType.PERSIST)   | |
Issue with orphanRemoval and multiple EntityManagers Hi, We have a problem where our database size grows over time more than expected. We've traced it down to the following issue: I have some entities that are using OneToMany relationship ... ; @ OneToMany (cascade=CascadeType.ALL, fetch=FetchType.EAGER, orphanRemoval=true)   | |
Extra uninitialised entities spawned on merge() In the following, Element is a base entity class, with a bi-directional @ManyToOne-@ OneToMany relationship Element owner - List ownedElements , and Example is a subclass entity with a relationship ... (); @ OneToMany (mappedBy = "owner",   | |
How to use JOIN FETCH?.MapKeyTemporal; import javax.persistence. OneToMany ; import javax.persistence.Persistence; import javax ... ; @ OneToMany @MapKeyTemporal(TemporalType.DATE) private Map addressHistory = new HashMap | |
"Failed to serialize instance" of Set problem Hi, I'm trying to persists objects defined as follows: @Entity @Inheritance(strategy = InheritanceType.SINGLE_TABLE) public abstract class AbstractContainer { ... @ OneToMany (fetch = FetchType.LAZY ... ObjectDB tries to serialize the collection using ordinary Java serialization ignoring the @ OneToMany | |
OEM enhancing Hello, I have question regarding OEM licence enhancement. @ OneToMany (fetch = FetchType.EAGER, cascade = CascadeType.ALL) private SomeClass[] props; @ OneToMany (fetch = FetchType.EAGER, cascade = CascadeType.ALL) private Map vars = new TreeMap (); Are these classes(SomeClass, SomeClass2), when not | |
NoSuchFieldError: __odbTracker on NetBeans 7.3 + JBoss 7.1.1 serialVersionUID = 1L; @ManyToOne @Index private City city; @ OneToMany (mappedBy = "owner") private List ... serialVersionUID = 33L; @ OneToMany (mappedBy = "city") private List persons; @ManyToOne @Index private Person | |
LazyInitialization / join fetch the fetch join? If so should I do to all fields of List , ie OneToMany or ... do to all fields of List , ie OneToMany or should also be done for joins ? Grateful. rafael_moreira Rafael | |
List of Enum Values in an entity LAZY to EAGER : private @ OneToMany (fetch=FetchType.EAGER) List flags; According ... that the @ OneToMany works here? Thank you Flashbaer Flashbaer Joachim Beig Eclipse is right. It shouldn't | |
PostUpdate collection null; @ OneToMany (fetch=FetchType.EAGER) private ArrayList myCollection = new ArrayList ... ; @ OneToMany (fetch=FetchType.EAGER | |
Weird behaviour with enhanced classes and embedded entities.persistence.Id; import javax.persistence. OneToMany ; import javax.persistence.Persistence; public ... ; int id; @ OneToMany (cascade = CascadeType.ALL, fetch = FetchType | |
orphanRemoval = true not working when CascadeType.REMOVE is disabled; @ OneToMany (orphanRemoval = true) private Set ... , addresses=[Address{name='name_2'}, Address{name='name_3'}]} I'm try use @ OneToMany (cascade | |
Merge with Parent/Child entities not possible.persistence.MapKey; import javax.persistence. OneToMany ; import javax.persistence.Persistence; import javax ... { @Id @GeneratedValue private long id; @ OneToMany (fetch = FetchType.LAZY | |
Is it possible to remove parent/child entities without refresh?.persistence. OneToMany ; import javax.persistence.Persistence; import org.junit.AfterClass; import org ... ; @ OneToMany (fetch = FetchType.LAZY, cascade = CascadeType.ALL, mappedBy = "parent | |
Left join fetch behaviour doesn't retrieve children? how much collection1 items we have in the bag ? ( and no matter kind of JPA annotation @ OneToMany , @ManyToMany ... we have in the bag? ( and no matter kind of JPA annotation @ OneToMany , @ManyToMany | |
TreeSet and compareTo() issue through a collection field in another class that uses eager fetch: @ OneToMany (fetch = FetchType.EAGER ... valid: @ OneToMany (fetch = FetchType.EAGER, cascade=CascadeType.PERSIST | |
composite index not used in query we defined a composite index for class Action: @Index(name="ssst",members={"startDate","state","subType","type"}) and an index for the OneToMany @ OneToMany (fetch=FetchType.LAZY) @Index public List objectsInCharge = new ArrayList (); on running a query like select count(a) from Action a JOIN | |
Problem with entities detection.persistence. OneToMany ; import javax.persistence.Table; import javax.persistence.Temporal; import javax ... ; @Embedded private Direccion direccion; @ OneToMany (mappedBy = "idAlumno") private List | |
Is there any restriction when using fetch=FetchType.LAZY ? am using in object declaration @ OneToMany (fetch=FetchType.EAGER, cascade = CascadeType.ALL) private ... @ OneToMany (fetch=FetchType.LAZY, cascade = CascadeType.ALL) private LinkedList referencedObj | |
Storing a tree of data (depth=3) (I've tried @ OneToMany , @Embedded and @ElementList) A role is a performer (I've tried inside that class ... of composers, list of tags and each of them are entity with @ OneToMany and are working fine (when I | |
How to move @Embedable collection to a dedicated entity class? we have a Parent and Child class with onetomany relation @Entity class Parent { @Id Long id; @ OneToMany (orphanRemoval = true, cascade = CascadeType.ALL) List children; } @Embeddable class Child{ @Id | |
Why are my Map entries not stored? private long id; @ OneToMany (fetch = FetchType.EAGER ... the Explorer. itsme Martin Petzold I have now changed to and it is working: @ OneToMany (fetch | |
Multiple Collection Fields not update correctly v2.8.8_2 I have an entity that has 2 collection fields: @ OneToMany (fetch = FetchType.EAGER) Collection position; @ OneToMany (fetch = FetchType.EAGER) Collection rotation ; Now if I persist them so the values are: position | |
New to Product & Having An Issue() { return name; } public void setName(String name) { this.name = name; } @ OneToMany (fetch=FetchType | |
"Problem" with cross join; @ OneToMany (mappedBy="ci") private List content; abstract class CIdata (@Inheritance(strategy=InheritanceType | |
GWT RPC is throwing serialization exception when I have object db date value will alway be empty after detaching. @ OneToMany (fetch = FetchType.EAGER, cascade = CascadeType | |
Problem with @OrderBy; @ OneToMany (mappedBy="defect") @OrderBy("seqRel, noteSeq | |
Are indexes implicitly created for relationships? Do the following annotations @ OneToMany @ManyToOne @ManyToMany @OneToOne imply @Index ? Thanks, Carl FastModel Ben Schreiber Actually these annotations (except @ManyToMany ) should apply @Unique on the @One side. But ObjectDB doesn't apply these indexes automatically | |
Different behavior with persist() and queried instances? Hi, We have a simple class that by itself contains (among others) a property pointing to a collection: class Bla { @ OneToMany (cascade = CascadeType.ALL) private List metaAttributes = new ArrayList (); } Now we do a simple em.persist(BlaInstance | |
NullPointer when accessing persistent field as follows; @ OneToMany (cascade=CascadeType.ALL, mappedBy="z_component") @MapKey(name="z_schemeName ... static class A { @ OneToMany (targetEntity = B.class, mappedBy ... .RemoteTestRunner.main(RemoteTestRunner.java:197) As before a Map structure was being accessed. @ OneToMany | |
After using the enhancer, Lazy loaded collections are no longer loading. They are set as null; } @Override public void setId(Long id) { this.id = id; } @ OneToMany (cascade={CascadeType.MERGE ... ; @ OneToMany (cascade={CascadeType.MERGE, CascadeType.PERSIST},   | |
spuriously objectdb objects have null references definitions are (for the null references above): ... @ OneToMany (fetch=FetchType.LAZY) @Index public List actions = new ArrayList (); ... @ OneToMany (fetch=FetchType.LAZY) @Index public List childNodes | |
NullPointerException on TreeSet load public static class MyEntity { @ OneToMany (cascade=CascadeType ... { @ OneToMany (cascade=CascadeType.PERSIST, fetch = FetchType.EAGER)   | |
com.objectdb.o.InternalException: java.lang.NullPointerException Hello, I have a CUIT entity, with a OneToMany List field called razonesSociales (that can be null): @ OneToMany (mappedBy = "cuit") private List razonesSociales; When I run this query it works ok: SELECT COUNT(item.sysID) FROM CUIT item WHERE ( (item.sysStatus.sysID=1) AND  | |
Tracking changes to new collections (in enhancement mode) after flush, CascadeType.DETACH }) private ModelElementImpl element; @ OneToMany (fetch = FetchType.EAGER, cascade ... ModelElementImpl element; @ OneToMany (fetch = FetchType.EAGER, cascade = {CascadeType.REFRESH | |
new objects not available in mappedBy associations Given a mappedBy association: e.g: @ OneToMany (mappedBy="department") public List employees; creating a new mapped class, e.g. new Employee, won't result in this object being available in the same transaction: ie: for (Employee e : department.employee) won't include the new object |