http://bugs.gpodder.org/show_bug.cgi?id=12
--- Comment #7 from Justin Forest <[EMAIL PROTECTED]> 2008-06-13 12:57:07 --- I am already subscribed to gpodder-devel, I am always on in Google Talk and I'll stay on IRC for a while (as umonkey). I thought of a separate "data provider" class, which would work with SQLite but could possibly be replaced with another backend (although I can't imagine why). It would have a few methods, much like the helper functions in gPodderLib work, indeed. It should also aggregate the data, e.g., things like newest_pubdate_downloaded() and get_episode_stats() are begging to be done with SQL. The more generic interface to access abstract properties of abstract URLs sounds simple, but it makes it impossible (or very complicated) to aggregate data on the server, so I'm against this. Two separate tables with separate fields for all properties gPodder uses is better. Also, this way it would be much easier to debug things with the SQLite console. But maybe these two can be combined. ;) Regarding the synchronization, I'll keep that in mind. -- Configure bugmail: http://bugs.gpodder.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes. _______________________________________________ gPodder-Bugs mailing list [email protected] https://lists.berlios.de/mailman/listinfo/gpodder-bugs
