Stefan Sperling wrote on Sun, Nov 28, 2010 at 16:48:30 +0100: > The real problem is that we want to be able to answer these questions > very fast, and some design aspects work against this. For instance, > FSFS by design does not allow modifying old revisions. So where do > we store the copy-to information for a given p...@n?
copy-to information is immutable (never changes once created), so we could add another hierarchy (parallel to revs/ and revprops/) in which to store that information. Any 'cp f...@n bar' operation would need to create/append a file in that hierarchy. Open question: how to organize $new_hierarchy/16/16384/** to make it efficiently appendable and queryable (and for what queries? "Iterate all copied-to places" is one). Makes sense? > The best idea we've had so far was using an sqlite database. But > that's really a hack around a design that doesn't support all the > features we want. > > Stefan
