About join

71-80 of 200Refresh
Forum
15

Join performance in Objectdb

annotated with @Id or @Index. In that case, executing the JOIN may require iteration over 160,000 x ... . Query 2 completed in 109 milliseconds (160000) The first query uses a JOIN on ID fields, similarly to your original query. The second query uses JOIN on direct references. The second form is simpler
Forum
15

Join query problem with new statetment

when using query with join. The query code is: TypedQuery inspirationQuery ... ) from Inspiration insp join insp.products p where (p.supplier = ?1 ... ) from Inspiration insp join insp.products p where (p.supplier = ?1
Forum
15

LEFT (OUTER) JOIN problem when mappedBy is defined

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
Issue
15

Problem with JOIN and inheritance

.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
Forum
15

"Problem" with cross join

=InheritanceType.JOINED) ... @ManyToOne private CI ci; subclass CIstring private String text; I ... fields in JOIN queries). Please try the new build (2.0.4_01) that should fix the bug. The attached test
Forum
14

joining of tables

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
Issue
14

Mapped by fields are not initialized by JOIN FETCH in queries

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
JPA Doc
14

javax.persistence.JoinColumn

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
JPA Doc
13

javax.persistence.MapKeyJoinColumn

) 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
FAQ
10

What are the main benefits of using ObjectDB?

that ability and require multiple tables, multiple records and join operations in order to support