On Tue, Feb 3, 2009 at 11:26 PM, haestan none <haes...@hotmail.com> wrote: > Hi, > > I'm trying to use Django for implementing new stuff in some of our legacy > apps. > All the existing apps use PostgreSQL as their database backend. Now in order > to > do this as transparent as possible, I'd like to use a different database > schema > for the contrib apps that come with Django (admin, sessions, etc.). > > Is this even possible? As far as I understand it by now, I don't see a way > to do > this. Can you confirm this or is there a way to move contrib apps into a > different > db schema?
Broadly speaking, this isn't possible. Firstly, Django doesn't provide any way to customize the tables that are used by contrib applications. An application specifies its own name, and it relies upon the required uniqueness of application names to avoid any naming conflicts. Secondly, Django doesn't currently contain formal support for schemas. This is mostly historical - nobody has had an itch big enough to scratch. That said, Ticket #6148 [1] is scheduled as a 'maybe' item for v1.1 [2], so there are plans to support database schemas. However, this ticket doesn't include any plans to allow for customization of schemas on a per-app basis. [1] http://code.djangoproject.com/ticket/6148 [2] http://code.djangoproject.com/wiki/Version1.1Features Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
