[
https://issues.jboss.org/browse/TEIID-5395?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5395:
---------------------------------------
I think things look mostly good also. However it looks like the old import code of adding
foreign keys based upon the collection side was for the case of a unidirectional
relationship so that may need to come back.
There is also another bug in that many to many relationships aren't generally handled
properly as the code won't create a bridge table.
I'll start building up some unit tests around import.
Improvement of JPA translator join behavior
-------------------------------------------
Key: TEIID-5395
URL:
https://issues.jboss.org/browse/TEIID-5395
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 10.2.1
Reporter: Harold Campbell
Assignee: Steven Hawkins
Fix For: 11.0
The behavior of the JPA connector has a number of issues regarding entity relationships.
* Implicit joins (those needed to get child entity id's) are made INNER JOINS,
preventing getting any rows where the value would be null.
* Something odd is done with *ToMany relationships which blows up the size of
resultsets.
* If a parent entity and a child entity use the same name for their id property, only one
gets mapped.
* It's not possible to join the same entity more than once.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)