Martijn Voncken wrote: >> I did some tests on this a while ago, and at the time I decided that the >> single metadata table wasn't fast enough. But I've learned a few more >> things since then. I think I'll have to redo the tests and see the >> results again. > Yes, do that tests. > query's on 2 or more attributes will/can be slow. > But how common are they in freevo now?
I don't know what hybrid tables are, but here are my requirements for freevo: - Fast access for directories. It would be great if I don't have to care about the media types there, so just return everything in the dir. This is the basic usage and should be very fast. - Search on some variables like 'everything from artist xy'. Exclude discs here, Freevo can't play discs that are not in the drive. - I need to store some variables to an item you don't know about when you create the db (plugins). And some ideas like I have in the mediadb now: - Every item has a cover. If not, use the cover of the directory. So when doing a query I need access to 'cover' for each item. So maybe make sure a dir always has a cover and add cover to every dir. Maybe add cover to everything, I don't care unless I can access it without searching the dir. - Find a way to add variables based on the mtime of the item. E.g. the directory stores how many items are in the dir. When the dir changes, this variable is auto-removed because it can't be right anymore (mediadb:store_with_mtime). This db would be a good think. Maybe we greate an extra process of it so other parts of the system may access it. Keep up the work Dischi -- Never put off until tomorrow what you can do the day after.
pgppJxdGJU6Vz.pgp
Description: PGP signature
