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] Commented: (OPENJPA-281) EAGER not the default fetch type without the @Basic annotation
Date Mon, 09 Jul 2007 18:30:04 GMT

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

Kevin Sutter commented on OPENJPA-281:
--------------------------------------

After a bit more discussion on the mail thread, I decided to ping Mike Keith (co-lead of the
JPA spec) on his interpretation of the 9.1.18 and 2.1.6 sections of the spec.  Here's his
response:

"You are correct. Lobs are to be treated like other Basic attributes and should default to
EAGER. Your colleague is somewhat justified in that lobs can be costly to load, however, once
we put lobs under the category of basic mappings we needed to be consistent and have them
use the same defaults. If they are expected to be both large and not referenced often then
@Basic(fetch=LAZY) should be used. Note that if one of these is not true then you probably
do want them to be eagerly loaded.

-Mike"

That should decide it.  This Issue will be used to change the behavior be consistent with
the @Basic annotation and make all listed types as EAGER fetch type by default.

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