On Mon, Dec 13, 2010 at 8:00 AM, Ryan Headley <[email protected]> wrote: > In my humble opinion. If this is something that can be farmed out to > cron, I wouldnt' even involve Django/Satchmo at all. Write an > external python script (or some other language if you are more > efficient) and do it directly. > > Ryan
Well, it's not something we can just plug into cron, and just hammering it out isn't as painless as it sounds; as we know, satchmo has a lot of tables and relationships so it's not necessarily a quick or easy job, though if we write it with a limited set of data, perhaps storing that query in a view, it is probably not super excruciatingly awful. And right now the atom feed from satchmo_ext.prodcut_feeds doesn't work at all for my primary set of data; the categories work (since they have far fewer products), but I want a full feed. The best thing would be to set up the templates so that they only call the database where the database hasn't already been retrieved. I'm not sure how dependent that is on Django convention, but if the category has already been retrieved by select_related(), product.get_category() should not ask the database for something that we already have. If it is currently not possible to obtain all of this data in one swoop, we really need to try to correct that. From Jeff -- You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en.
