From: Kevin <ke...@dr...> - 2005-12-12 18:21:33
|
The issue on where to stick the feed image url got me thinking... Q: Why do we need to store the image URL in the database at all? More generally, why do we need to store any of the extra RSS feed info in the DB? I'm not saying eliminate the feed table, just trim it down to what is absolutely necessary to maintain the relationships between the entities i= n the DB. For the following columns, what I am suggesting is use the magpie rss cache as the only place where the data is stored for the application.=20 Magpie does a great job with caching the parsed RSS/Atom data structure.=20 So, I don't think we will see much of a performance hit from doing it thi= s way. I've only listed the non-critical attributes for a feed. The interface will not brake horribly if these are not available. (ex: cache file missing and feed is down) * description * latitude * longitude * type * image Comments? --=20 Kevin |