On 6/7/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > Those are two I can think of off the > top of my head; there are other instances, though.
For dbsettings at least, I expect a dynamic settings.SITE_ID would be even more damaging. It loads settings from the database once during startup and only touches the database again when updating them. So all "sites" would end up with the same dbsettings, even though they shouldn't. When updating them, it would assign them to the appropriate site, which would then be used throughout that instance. Unfortunately, this would be reset the next time the server starts, so you'd have to manually set all your settings on every site every time you start the server, in order to get them to work properly. The only around this for dbsettings would be to maintain a dictionary mapping each SITE_ID to its dbsettings cache. I don't enjoy that thought, especially since it would be a rare case that someone would want to do it.. -Gul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
