The filters would then be stored independently for every library. I'm not sure that's what everyone would want... if you define filters you want to use with all your libraries, I would then have to add a lot of UI elements and database code to persist filters across every library that is currently defined, and add options to copy or move filters between libraries. It just starts adding more and more work, but I don't really think it's necessary to save the filters inside the database, because I can just save a name instead of an ID, and that should work fine. I'll think about this some more though.
Mike
Mike