On Sun, 2005-08-21 at 19:53 +0200, Martijn Voncken wrote: > i did a little test on that,most of the time is in python.
We have to count that time too. What we're experimenting with now is what implementation is going to be faster. > your-test: all static info from this directory. > my-test:all dymanic info from this file. I wouldn't suggest to implement it where you need to query multiple tables for one file. My approach puts all the metadata needed for one file into a single row. For a single directory, then it queries multiple tables. One row provides all metadata associated with that file. (What do you mean by "static" and "dynamic" info?) My test demonstrates that the table-per-filetype, column-per-attribute approach is faster by a significant margin at least for the most common use-case of getting a list of all files in a directory, and, intuitively, it would be faster for other queries simply by virtue of the fact that there are significantly fewer rows to iterate. I don't think your test code is very representative of an actual implementation. At least, that's not how I implemented things in the prototype I attached earlier, so you're comparing apples and oranges. But I'm definitely interested if there's a faster approach than what I implemented. :) Cheers, Jason.
signature.asc
Description: This is a digitally signed message part
