About INNER JOIN

91-100 of 200Refresh
Issue
5

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
4

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
3

What are the main benefits of using ObjectDB?

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

WHERE clause (JPQL / Criteria API)

language from a specified set of languages: SELECT c, l FROM Country c JOIN c.languages l WHERE c
Manual
3

DELETE Queries in JPA/JPQL

cannot include multiple variables and JOIN, and cannot include the GROUP BY, HAVING and ORDER BY clauses
Manual
3

SELECT clause (JPQL / Criteria API)

can be added to the SELECT clause by using a bound JOIN variable in the FROM clause. Nested path expressions
Manual
3

JPA Criteria API Queries

, construct). FROM clause (from, join, fetch). WHERE clause (where). GROUP BY / HAVING clauses (groupBy
JPA Doc
3

JPA Queries

variables, join and fetch): Other criteria query expressions (for all the query clauses):
Manual
3

UPDATE SET Queries in JPA/JPQL

variable name) for iteration. Multiple variables and JOIN are not supported. The SET clause defines one or
Manual
3

Online Backup

.join(); // Wait until the backup is completed.     // Do something with the backup (e.g. upload