About INNER JOIN

71-80 of 200Refresh
JPA Doc
7

joinSet(attributeName)

Method javax.persistence.criteria.From SetJoin joinSet(   String attributeName ) Create an inner join to the specified Set-valued attribute. Parameters: attributeName - name of the attribute for the target of the join Returns: the resulting join Throws: IllegalArgumentException - if attribute of the given name does not exist Since: JPA 2.0
Forum
7

Issue with Casting / Joins

MyEntity(); entity.getEmbeddeds().put("test", new EmbeddedA); ... // Try to query using join From from = criteria.from(MyEntity.class); MapJoin join = from.joinMap("embeddeds"); Path pathToEmbeddedAName = join.value().get("name") <-- fails with attribute "name" not found
JPA Doc
7

Criteria Query From Elements

(bound by an entity class) are represented by the Root subinterface: Join variables (bound by an attribute of a preceding variable in the FROM clause) are represented by the Join subinterface and its descendant interfaces: See the FROM in Criteria Queries section for more details and examples. Join
Forum
7

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
7

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

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
7

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

Issue with full cross joins

hi, There seems to be an issue with full cross joins & maps. This query: SELECT  $1 FROM com.lexware.vereinsverwaltung.verein.mitglied.Mitglied  $1 LEFT JOIN $1.qubletFRAGMENTMAP $4 ... values in JOIN has not been implemented and a map was handled as a collection of the first half
Forum
7

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
7

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