On 4/14/06, Ed Epstein <[EMAIL PROTECTED]> wrote:
> If you think it's a good idea, I'd probably suggest looking at adding a
> per project per app setting that specifies a schema. It would need to
> add the create schema statement during the initsql process. For
> subsequent accesses, we would set the default search path for the life
> of connection to match the schema specifed in the settings. Is this
> worth pursuing?
That's the big question -- should the schema be specified in the
settings file or in the model? (Well, I've never used schemas, so
maybe it's not as big of a question as I'm making it out to be. Maybe
it doesn't make sense to put the schema in the model?)
I forgot to mention this ticket, which has a patch for adding schema support:
http://code.djangoproject.com/ticket/1051
That's on an older version of Django but may give you some ideas.
Adrian
--
Adrian Holovaty
holovaty.com | djangoproject.com
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
