Użytkownik Paul McNett napisał: > + # I think both are wrong. In #1, you'd never > get a requery of that child if there was > + # one changed record in the hierarchy, plus > there are performance issues in running > + # that check. In #2, you'd never get a child > requery unless RowCount was 0. I'm leaving > + # both of those conditions out completely for > now, although that is most certainly > + # wrong as well, but at least we are now > consistent in behavior between e.g. self.first() > + # and self.RowNumber = 0.
Hi. I think, we should distinguish between common database tasks like querying and fetching, which is part of querying process. Because of performance reasons, framework fetching process is splitted and deferred in time. We issue query request only if filter condition changes or user request it. Then data are fetched as they are needed if parent context changes. What if I don't want to requery children on navigate, but still need every node in my data chain get fetched after requery? Do I really need to move pointer and push requery button on every row? 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. -- Regards Jacek Kałucki _______________________________________________ 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]
