This is an interesting idea that I wouldn't have thought of. However, I'm not sure that every select is equal to a display. For example if I load the objects via the admin.
Also, I am not sure as there would be a huge gain as the same number or queries would still be executed, however in this case the database is initiating some of them instead of Django. Steve On Aug 24, 5:59 am, TiNo <[EMAIL PROTECTED]> wrote: > Maybe this could be a > solution:http://www.stardata.it/articoli_en/triggers_on_select_articoli_en.html > > No idea how much overhead that would create though. > > On Sun, Aug 24, 2008 at 5:43 AM, Steve Potter <[EMAIL PROTECTED]>wrote: > > > > > I am working on a project that involves logging every time an object > > is displayed, and I can have anywhere from tens to hundreds of objects > > displayed per page. > > > So needless to say I can quickly be generating very large numbers of > > queries to the database to log all of these displays. > > > What I am looking for is some method of write caching these logs so I > > only write to the database every 'n' times the object is displayed, or > > when the cache gets too old. > > > Has anyone done anything like this? > > > Maybe someone just has a better suggestion for how to log this data > > with less DB queries? > > > Thanks, > > > Steve --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
