this query: "SELECT i FROM Invoice i LEFT OUTER JOIN i.itemList items" But this query never returns ... JOIN works correctly. Is this normal behaviour? Thank you Michael Sample application
public ... Invoice i LEFT OUTER JOIN i.itemList items");
List resultList = query.getResultList

.customer.VendorCustomer $1 JOIN $1.qubletFRAGMENTMAP $2, com.quasado.foundation.warehouse.contract ... I do select from "VendorCustomer" yet through using the join, he is also selecting all "Customer ... should not even join the $1.qubletFRAGMENTMAP of any other class but "VendorCustomer"!? thanks Alex My bad, 2.4.0 seems to fix it. quasado

a column for joining an entity association or element collection. If the JoinColumn annotation itself is defaulted, a single join column is assumed and the default values apply. Example ...
@JoinColumn(name="CUST_ID") // join column is in table for Order
public Set

Hi In objectdb site i found :Note: This ORM/SQL annotation is silently ignored by ObjectDB so i want join tow table and generate a third table. Ex: table 1: employee table 2: address and the generate table will be table 3: emp_add employee: e_id, e_name address: add_id, city, house

As demonstrated in this forum thread, a mapped by collection field with lazy fetch mode is not initialized in results of a query that uses JOIN FETCH on that collection field (when enhancement is used). Build 2.4.1_06 fixes this issue (fields are now initialized and the test in the forum passes

) Specifies a mapping to an entity that is a map key. The map key join column is in the collection table, join table, or table of the target entity that is used to represent the map. If no MapKeyJoinColumn annotation is specified, a single join column is assumed and the default values apply. Example 1