"Bert Huijben" <b...@qqmail.nl> writes: > Another option (good or bad) would be to just update the code to create > format 29 working copies to create different indexes. > > Our use of SQL would ensure that we would get the same result with the old > or new indexes, but working copies created with newer clients would be > faster than those that use the original format 29. > > A future format 30 bump could then upgrade slow 29 working copies to the > same format 30. > (This may or may not be possible using our compatibility guarantees)
I suppose it is possible, but it would make it more difficult to respond to reports that 1.7 is slow. We would have to determine if the working copy had the correct indices, either by asking for it to be reproduced in a new working copy or by querying the wc.db file. -- uberSVN: Apache Subversion Made Easy http://www.uberSVN.com
