openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Geraldo Xexéo (JIRA) <j...@apache.org>
Subject [jira] Created: (OPENJPA-694) @SecondaryTable expected behavior is INNER JOIN?
Date Fri, 15 Aug 2008 18:17:44 GMT
@SecondaryTable expected behavior is INNER JOIN?
------------------------------------------------

                 Key: OPENJPA-694
                 URL: https://issues.apache.org/jira/browse/OPENJPA-694
             Project: OpenJPA
          Issue Type: Question
          Components: docs, jpa
         Environment: Any
            Reporter: Geraldo Xexéo


I have some code running that makes me believe that the @Secondarytable annotation has the
INNER JOIN behavior. 

I checked both the original JPA specification and many implementations and none of them talks
about the subject. Hibernate, however, has this in the documentation.

Can you confirm it? It has a lot of side effects, for example:

1) Some implementations will not create a row in the secondary table if all the fields are
NULL, this will make an object impossible to retrieve or edit. (since the inner join will
return null, but it will exist on the primary table).

2) Rows from legacy tables that can´t be extended, a good reason to use secondarytable, will
not be retrieved if we do not create, probably "out of the box", rows in the secondary table,
even if we don´t have any information to fill there.

Can you answer on the implemented behavior and comment on my two examples?

Should this be pointed to JPA specification responsibles?

Thanks,
xexeo


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message