openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Sutter (JIRA)" <j...@apache.org>
Subject [jira] Updated: (OPENJPA-281) EAGER not the default fetch type without the @Basic annotation
Date Thu, 02 Aug 2007 13:12:53 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kevin Sutter updated OPENJPA-281:
---------------------------------

    Attachment: openjpa-281.patch

I decided to post a patch for this Issue before committing it in order to get feedback first...
 Take a look at FieldMetaData and see how I am determining whether to include a given type
in the default fetch group.  Although it looks a little strange to be doing all of this testing
for Serializable, Enums, and Lobs, it actually limited the changes to this single part.  Other
alternatives started to ripple through out the code base and I didn't see where it was buying
anything.  If I don't hear anything negative, I'll commit these changes later today.

I also updated AllFieldTypes and created a new TestBasicAnnotation testcase so that we don't
accidentally re-introduce this problem.

The other change to FieldMapping.java was to avoid an obscure NPE when parsing some orm.xml.

Thanks,
Kevin

> EAGER not the default fetch type without the @Basic annotation
> --------------------------------------------------------------
>
>                 Key: OPENJPA-281
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-281
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jpa
>    Affects Versions: 0.9.7
>            Reporter: Kevin Sutter
>            Assignee: Kevin Sutter
>             Fix For: 1.0.0
>
>         Attachments: openjpa-281.patch
>
>
> There's an on-going discussion on the dev mailing list concerning this problem (http://www.nabble.com/Eager-fetching-not-working-with-enums-and-lobs-tf4037105.html).
 Since I've gotten agreement on at least one aspect of the problem, I decided to open this
JIRA Issue to document the problem.
> Here's a summary of the problem:
> I am finding that the supposed default action of Eager fetching is not happening with
@Enumerated and @Lob fields.  If I explicitly specify the @Basic annotation, then the fields
are eagerly fetched.  But, without this extraneous @Basic, these fields are lazily loaded.
 This action does not seem to be consistent with the spec.  Nor, can I find any mention of
this alternate behavior in our OpenJPA manual.  Sounds like a bug to me.  Any other insights?
> This works (eager loading kicks in):
>     @Basic @Enumerated(EnumType.STRING)
>     private Gender gender;
> This does not work (lazy loading kicks in):
>     @Enumerated(EnumType.STRING)
>     private Gender gender;
> I have also tried to use defaults (without any annotations), and lazy loading still kicks
in:
>     private Gender gender;
> The JPA spec attempts to address this situation in section 9.1.18...  Section 9.1.8 of
the JPA spec indicates that @Basic is optional and applies to the following types: 
> "..Java primitive types, wrappers of the primitive types, java.lang.String, java.math.BigInteger,
> java.math.BigDecimal, java.util.Date, java.util.Calendar, java.sql.Date,
> java.sql.Time, java.sql.Timestamp, byte[], Byte[], char[], Character[],
> enums, and any other type that implements Serializable."
> And, since the default fetch type for @Basic is EAGER, it looks like we need to do eager
fetching for both @Enumerated and @Lob fields unless otherwise overridden by a LAZY fetch
type (ie. @Basic(fetch=LAZY)).  Agree?
> We're still working on the agreement...  :-)
> Thanks,
> Kevin

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