{"shas":[["ffb35361f9dbb2f2ff8a530dab33ac10053f386c","e6ed735dee2bba2ae203a2baa5deb443ba766cdf@57a73879-2fb5-44c3-a270-3262357dd7e2","- Optimisation: Late evaluation of Multilinks (only in rdbms backends):\n  previously we materialized each multilink in a Node -- this creates an\n  SQL query for each multilink (e.g. 'files' and 'messages' for each\n  line in the issue index display) -- even if the multilinks aren't\n  displayed. Now we compute multilinks only if they're accessed (and\n  keep them cached).\n- Add a filter_iter similar to the existing filter call. This feature is\n  considered experimental. This is currently not used in the\n  web-interface but passes all tests for the filter call except sorting\n  by Multilinks (which isn't supported by SQL and isn't a sane concept\n  anyway). When using filter_iter instead of filter this saves a *lot*\n  of SQL queries: Filter returns only the IDs of Nodes in the database,\n  the additional content of a Node has to be fetched in a separate SQL\n  call. The new filter_iter also returns the IDs of Nodes (one by one,\n  it's an iterator) but pre-seeds the cache with the content of the\n  Node. The information needed for seeding the cache is retrieved in the\n  same SQL query as the ids.\n\n\ngit-svn-id: https://svn.roundup-tracker.org/svnroot/roundup/roundup/trunk@4581 57a73879-2fb5-44c3-a270-3262357dd7e2","schlatterbeck"]],"repo":"hemmecke/roundup-svn","actor":"hemmecke","ref":"refs/heads/master","size":1,"head":"ffb35361f9dbb2f2ff8a530dab33ac10053f386c","actor_gravatar":"720a4dc26c1296b89cf8befadfb1f0b6","push_id":27190209}