Hi Tom, It should work to set up your own sites model with the same table name, as long as you can change all foreign keys to point to _your_ site model.
Are you actually using more than one site? Collin On Friday, December 12, 2014 7:57:21 PM UTC-5, Tom McKenzie wrote: > > Hello All > > Is there a way to cache the database queries for django.contrib.sites? We > are running 1.4.15 at the moment and we planning to upgrade to 1.7.x soon. > > Can I setup my own "custom" sites model with the same fields so I don't > have to change the database table name? > > I have been trying Cache machine with good success on our other models. > Ideally I would like to use it for the sites too. > > Thanks, > Tom > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/130ff7c2-1d4c-48ba-9d85-f25f65a639b8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
