On 06.09.2010 12:16, Philip Martin wrote:
> To use a per-directory query strategy we would probably have to cache
> data in memory, although not to the same extent as in 1.6. We should
> probably avoid having Subversion make status callbacks into the
> application while a query is in progress, so we would accumulate all
> the row data and complete the query before making any callbacks. Some
> sort of private svn_wc__db_node_t to hold the results of the select
> would probably be sufficient.
I wonder if per-directory is really necessary; I guess I'm worrying
about the case were the WC tree has lots of directories with few files.
Do we not have the whole tree in a single Sqlide DB now? Depending on
the schema, it might be possible to load the status information from the
database in one single query.
(On a side note ... it's all very well to shun specialized caching and
expect your database layer do do it for you [optimally], but I see no
reason to believe that Sqlite would be significantly better at that than
Received on 2010-09-06 12:27:15 CEST