#: by Pablo Ruggia's words the mind was *winged* :#
lazy = false is not a really solution. If you set lazy to false, hibernate
always load the collections. You don't get LazyInitializationException, but
you read database more than you have to.
Hibernate.initialize() does the job. But you have to do it manually whenever
you know that you may be will use that collection. So, if you didn't use it,
you bring that collection from database with no need.
And your patch is able to retrieve a record only if accessed?
But this may create a lot of network trafic (not to count the N queries). Moreover how are handling
locking when you are not in read-only mode?
Even if at first sight Hibernate solution doesn't look so appealing I think it
is a good decission.
Sorry I have to disagree with your solution.
:alex |.::the_mindstorm::.|
On 7/25/05, Alexandru Popescu <[EMAIL PROTECTED]> wrote:
#: by Pablo Ruggia's words the mind was *winged* :#
> I know, it has to be much more configurable. But hibernate user lists or
> forums are just so unfriendly. Every once I post a question about lazy
> initialization, they kind of get ungry.
>
> On 7/25/05, Henri Dupre <[EMAIL PROTECTED]> wrote:
>>
>> That's a nice solution that hibernate patch... But I don't feel
>> confortable patching hibernate... Have you submitted your solution to
>> the Hibernate JIRA? This behavior should be customizable through the
>> hibernate configuration.
>>
>>
>> Thanks,
>>
>> Henri.
>>
>
How is your solution different lazy=false or Hibernate.initialize()? (i
must confess i read it quite
fast)
:alex |.::the_mindstorm::.|
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
