I have currently done a project for a customer and I can not "finish" it off and give it out to the customer due to performance issues as half the database is loaded into memory...the whole object graph is loaded even when it is not used. To me this would be quite urgent.
How do you all live with Trails without lazy fetches? Have you all done some "custom" bug fixes or are your application not using many related database objects?
-------- Original-Nachricht --------
> Datum: Tue, 29 Apr 2008 09:28:49 -0400
> Von: Ken in nashua <
nhhockeyplayer@...>
> An:
users@...
> Betreff: RE: [trails-users] Lazy Fetches
>
> 1.2 has some corner cases that I have to override custom to keep it air
> tight. The 1.1 and 1.2 persistence models have a resemblance. The new model
> has shown to be a bit more flexible in resolving use cases. I would probably
> prepare for no action since 1.1 has been left behind.
>
> Best regards
>
> Ken in nashua
>
>
>
> > Date: Tue, 29 Apr 2008 12:45:05 +0200
> > From:
superoverdrive@...
> > To:
users@...
> > Subject: [trails-users] Lazy Fetches
> >
> > Would it be possible to support Lazy Fetches in trails 1.1? (an update?)
> > Or would those changes take too long so the time is better invested in
> working on trails 1.2 ?
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this list, please visit:
> >
> >
http://xircles.codehaus.org/manage_email> >
> >
>
> _________________________________________________________________
> Make i'm yours. Create a custom banner to support your cause.
>
http://im.live.com/Messenger/IM/Contribute/Default.aspx?source=TXT_TAGHM_MSN_Make_IM_Yours---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email