in this instance we're not caching for output... there are some very expensive sql queries on ArtWeLove.com
to alleviate that, i create an object per-artist / venue / show / etc and store it in memory for 15minutes these objects have the basic sql table, some extended sql queries, and between the two there are some eagerloaded objects to get around the issue, i am saving the eager objects separately. in the future these objects will be serialized to json/yaml or something similar for use in php/perl.. however i thought this behavior was worth bringing up. took me forever to figure out what was going on. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
