About LEFT OUTER JOIN

81-90 of 200Refresh
Forum
3

InternalError on multiple AND and JOIN Query

Hi, Using objectdb 2.2.8_06. Running the following query: SELECT DISTINCT $1 FROM CDI $1 JOIN $1.contactDetails $2 JOIN $2.addresses $3 JOIN $3.attributeList $4 JOIN $2.phoneNumbers $5 JOIN $5.attributeList $6 WHERE ((($4.name='suburb') AND ($4.valueAsString='Los Angeles')) AND (($6.name='areacode
Forum
3

Lazy Init / Eager / Join Fetch collection strategy ? What to choose ?

,join fetch seems to be the right choice. What about ObjectDb ? The implementation is totally different. Is an "All eager strategy" more efficient that many join fetch ( cartesian product + distinct ... all strategy" Or "Fetch Join strategy" for ObjectDb ? Regards, Xirt > Is an "All eager strategy
JDO Doc
3

addSubquery(sub, variableDeclaration, candidateCollectionExpression, parameters)

is composed as a Query and subsequently attached to a different query (the outer query) by calling ... of the outer query. Only some of the query parts are copied for use as the subquery. The parts ... is the expression from the outer query that represents the candidates over which the subquery is evaluated
Result
3

ObjectDB version 2.4.0

web application (by catching unexpected exception). Fixed LEFT [OUTER] JOIN issues (including ... expressions in queries. Fixed handling null values in JOIN and path expressions in queries. Fixed a possibly
Issue
3

Different behavior for two equal queries

through null in one of the OR components. Navigation should be compiled as LEFT OUTER JOIN to avoid losing results in such cases, but maybe an ordinary JOIN was used in this query. Could you isolate the OR
Forum
3

How to use JOIN FETCH?

JOIN FETCH to avoid excessive round trips to the database: SELECT c FROM Country c JOIN FETCH c ... .   TypedQuery q = em.createQuery(         "select p from Person p join fetch p.addressHistory ... then this is normal for JOIN FETCH and you can remove duplication by using SELECT DISTINCT. The main problem
Forum
3

Multiple joins did not return expected result

a specific calendar by its id like: SELECT event FROM Calendar c1, SharedCalendar c2 INNER JOIN c1.events AS event INNER JOIN c2.original.events AS event WHERE c1.id=?1 OR c2.id=?1 Unfortunately ... JOIN c1.events AS event1 INNER JOIN c2.original.events AS event2 WHERE c1.id=?1 OR c2.id=?1 instead
Forum
3

Detaching objects after JOIN FETCH

Hi, I have a question about detaching objects after issuing query with JOIN FETCH. Let's say I ... to fetch all B classes with all A classes skipping lazy loading: select b from B b join fetch b ... is closed, B.aClasses is always null. I thought, that after join fetch and CascadeType.DETACH list
Forum
3

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
3

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