Comment #2 on issue 7 by n.leush: Cache unexisting db teampltes entries http://code.google.com/p/django-dbtemplates/issues/detail?id=7
I've already posted my solution in http://code.google.com/p/django-dbtemplates/issues/detail?id=5&can=1#c2. Wnen template doesn't exists "False" is cached. So next time while reading template from cache we can get "None" (which means template should be read and cached) or "False" (wich means no template was found in db previously). When user will create template in admin - post_save signal will override cache record. As for me its suitable. Is it bad solution? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pinax-updates" 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/pinax-updates?hl=en -~----------~----~----~----~------~----~------~--~---
