On Thu, 2007-06-07 at 20:00 -0400, Marty Alchin wrote: > 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.
No dbsettings depend on SITE_ID, as far as I can see. I think you are just confusing multiple issues here. This thread is not at all about making all settings dynamic based on SITE_ID. It was about making the functionality currently provided by SITE_ID dynamic (just the value of SITE_ID -- or it's new equivalent). Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
