On Tue, 03 May 2005 01:31:59 +0200, Gavin King <[EMAIL PROTECTED]>
wrote:
Yes, you're misunderstanding.
If I say lazy="false", it should *always* be eager fetched.
ok got it! Like it!
But we need to make it *very* clear in the release notes.
/max
There's nothing wrong with fetch="join" lazy="tru
On May 3, 2005, at 1:31 AM, Gavin King wrote:
There's nothing wrong with fetch="join" lazy="true" if you want
flexibility.
I hate explaining this already...
---
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and
Yes, you're misunderstanding.
If I say lazy="false", it should *always* be eager fetched.
There's nothing wrong with fetch="join" lazy="true" if you want
flexibility.
-Original Message-
From: Max Andersen
Sent: Monday, 2 May 2005 5:48 PM
To: Gavin King; Christian Bauer; hibernate-devel@
Note that the association-level lazy setting is now *completely
respected*. if I run a HQL query and some of the objects in the result
set have non-lazy associations, those associations will be
*immediately fetched*.
This one I don't get why we want that ?
I actually saw it as a strength that you
All code/artifact generating tools are in hibernateext/tools.
There you find code that generates via velocity templates and/or
actual programmatic building of a Configuration.
/max
omg please excuse my sentence structure. no sleep. my code is better,
promise. :-P
--
"No tengo pelos en mi lengua"
