Emmanuel Bernard wrote:
(1) make lazy default to true on both and
mapping elements; if a class cannot be proxied, laziness
is transparently disabled; make it clear that we intend
laziness to be used 99% of the time
Most controversial part but I'm +1 from a pragmatic perspective.
Howeve
* The default should be fetch="select" for collections, what
should the default be for to-one associations? I suppose
that purely for backward compatibility purposes we need
fetch="auto|join|select", where auto is the default, and
chooses "select" for a lazy-enabled class.
Keep the "auto" and t
If you require immediate answers, you need commercial support:
http://hibernate.org/SupportTraining/CommercialSupportAndTrainingForHibernate
Michael Mehrle wrote:
I did - and nobody is replying! Can someone just answer my question?
---
This SF.N
I did - and nobody is replying! Can someone just answer my question?
- Original Message -
From: "Emmanuel Bernard" <[EMAIL PROTECTED]>
To: "Gavin King" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Sunday, September 12, 2004 11:44 PM
Subject:
Gavin King wrote:
In my private chats with people, it seems we all agree that
currently, Hibernate2 association fetch strategy configuration
is confusing and has nonsensible defaults. I've spent quite a
lot of time thinking about how we could clean this up without
breaking 2.x mapping documents to
Hi!
(1) make lazy default to true on both and
mapping elements; if a class cannot be proxied, laziness
is transparently disabled; make it clear that we intend
laziness to be used 99% of the time
+1
Hm - i can't remember, does lazy=true on a non-proxyable class fail
today ? (with
a error
In my private chats with people, it seems we all agree that
currently, Hibernate2 association fetch strategy configuration
is confusing and has nonsensible defaults. I've spent quite a
lot of time thinking about how we could clean this up without
breaking 2.x mapping documents too much, and come to
