Jason Tackaberry wrote: >> Still, what happens to bad files kaa.metadata can't parse? Where >> should I add them? A guess a 'generic' table needs to be added. But >> again: what happens when a file is identified later and is moved from >> 'generic' to 'image'? > > Or add them to the image (or whatever) table, and just not fill in those > attributes. The application should be able to handle such cases anyway, > it seems to me.
I should put a fxd file to images? Fxd files are known to Freevo, but I don't want to register a special table for it. > I didn't really foresee putting into the database files which aren't > indexed (or file types which aren't known). What would be the point? I > suppose if you want to avoid a listdir(), but does avoiding listdir() > really save a whole lot in the common case? I want to get the mtime of the dir. If it is still the same, I try to avoid os.listdir. No point in doing that. But when freevo doesn't know about files with the extention .foo, I need to put it somewhere in the db. It should be returned. And if I just put stuff in a generic table, a new app knowing about this has to correct it. So I guess I won't put non index files in the db, moving won't be a problem. And a generic table will do the trick. Dischi -- Take care to get what you like, otherwise you will be forced to like what you get.
pgpnrTQ5Tm81c.pgp
Description: PGP signature
