On 10/27/11 11:49 AM, Paul McNett wrote: >> > Solution is to use large ChildChacheInterval property value. >> > BTW, big disadvantage in performance is default value of this property. >> > It causes instant data requery on every record pointer move, e.g. when >> > navigating across the grid. >> > By default it should be set to reasonable value like 30 sec or even more. > I agree in principle, however my testing of setting the cache interval != 0 > in the > past has always resulted in trouble. I never had time to dig, but I was > getting > children and/or grandchildren in the wrong context, but not all the time. I > couldn't > rely on it. > > Perhaps recent changes have fixed it - in particular, the recent change I > made to > ensure that the current parent is updated even if the requery isn't going to > happen > could explain by prior experience.
I've been playing with ChildCacheInterval and it seems like it is working just fine now. I think the last time I really tried to get it working was about a year ago, so something we've done since then took away the problems I was having. Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
