ObjectDB ObjectDB

Internal Website Search

51-60 of 200 resultsRefresh
99

Left join fetch behaviour doesn't retrieve children?

Hello, I'm a little bit confused about a left join fetch behaviour. In this test case, i try to fetch my 3 children using a left join fetch. But my collection is null after closing the em ... left join fetch         em = emf.createEntityManager();         TypedQuery<MyEntity> query
93

LEFT JOIN FETCH over empty embedded collection returns no results

First of all, thank you for promptly implementing JOIN FETCH over nested paths in response ... , but I attempt to LEFT JOIN FETCH all the members of a collection within a (non-existent) member ... where bList is empty, the following works (returns my instance of C): SELECT c FROM C c LEFT JOIN FETCH
89

multiple LEFT JOINs do not work as expected

like this: SELECT DISTINCT $1 FROM Organisation $1 JOIN $1.attributeList $2 LEFT JOIN $1.parentOrg $3 LEFT JOIN $3.parentOrg $4 WHERE ((($2.name='Attribute1') AND ($2 ... , since I use LEFT Joins this query should return all organisation under the root organisation
88

How do I achieve a Deep Fetch using JOIN FETCH?

that I can express one level of eager fetch in JPQL as follows: SELECT c FROM C JOIN FETCH c.bList WHERE c.id=:id But when I attempt to take it to the 2nd level: SELECT c FROM C JOIN FETCH c.bList JOIN FETCH c.bList.aList WHERE c.id=:id I get an error along the lines of: Invalid fetch path
88

LazyInitialization / join fetch

descrica2_2_3_ from the User usuario0_ left outer join on area area1_ usuario0_.codigo_area = area1_.codigo left outer join on User usuario2_ usuario0_.codigo_chefe = usuario2_.codigo left outer join company empresa3_ on usuario2_.codigo_empresa = empresa3_.codigo left outer join on specialty especialid4
88

Query with FETCH JOIN returns multiple results instead of one.

jpqlResult = em.createQuery( "SELECT d FROM Demand d JOIN FETCH d.services WHERE d=:demand ... duplicates with DISTINCT: SELECT DISTINCT d FROM Demand d JOIN FETCH d.services WHERE d=:demand ... : SELECT d FROM Department d LEFT JOIN FETCH d.employees WHERE d.deptno = 1 "A fetch join has the same
87

Issue with Casting / Joins

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

ObjectDB Object Database Features

(extremely fast JOIN queries). Map keys and values are indexable. Nested paths inside embedded objects ... Automatic pre-loading optimizations. Configurable JPA eager/lazy fetch and JPA query FETCH JOIN ... (first, max) - for paging. Query Structure SELECT (including NEW). FROM (including INNER JOIN, LEFT
20

javax.persistence.criteria.Fetch

javax.persistence.criteria Interface Fetch<Z,X> Superinterfaces: FetchParent<Z,X> Represents a join ... a fetch join to the specified attribute using an inner join. Create a fetch join to the specified attribute using an inner join. Parameters: attributeName - name of the attribute for the target
18

javax.persistence.criteria.FetchParent

, Join, ListJoin, MapJoin, PluralJoin, Root, SetJoin Represents an element of the from clause ... a fetch join to the specified attribute using an inner join. Create a fetch join to the specified attribute using an inner join. Parameters: attributeName - name of the attribute for the target

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support