This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I have just updated my LS 5 installation with the latest nightly build. The last time I did this was 13 Dec 2013. Before this nightly update, I had no problem regarding Eager Loads, but now, collections that did not eager load previously are eager loading, and it is killing my applications performance. I have a series of tables. One called HotelBooking, that has a many to one relationship with a table called Guest, as well as many other tables. The join mentioned has a Back Reference Aggregate called FullBooking. So if I open Guest, it should only load guest, no bookings. Again if I open booking, it does not eager load guests, unless I specify the Back Reference Aggregate of FullBooking. Before the update, this worked correctly. Since the latest nightly build was installed every Guest record I open is opening all related HotelBooking records, and all onwards related tables, so it is taking ages, as in 20+ minutes to open the form. Where previously it took about 3 seconds. Has anything changed in these recent nightly builds that would account for this change? I have checked the operation by using a computer that was not yet updated, and it opens in 2 to 3 seconds. With identical code, and only the new Lightspeed dll's it now takes minutes. I would welcome all advise on this, anything that doe snot involve me recoding the entire data level and business levels to adapt for the new Eager load operations. Thanks |
|
|
|
|
Hmm, there has only actually been 1 change in the runtime since that date and that is in relation to fixing a bug with entities which have a LockVersion and are being maintained in the 2nd level cache. Can you recheck the version # on the runtime assemblies where this was working? Also if its possible to send us through a small repro I can have a look into what might be happening here. I would suggest you rollback to the earlier version in any case as its highly unlikely any of actual changes since that date would be of specific interest.
|
|
|
|
|
Hi Jeremy, The version that we are using that works is version 5.0.2335.0. We have reverted back to this version, and our program is running normally. I will try to put together a small project for you. But I am not sure when I will get time to do this. On a side note, One thing I requested some time ago was a change log for the Nightly Builds, so we know if we need to update, and also if we experience a problem we know if the nightly build could be responsible. Maybe now would be a good time to reconsider this. ;-) Best regards Mark |
|
|
|
