On 1/6/07, Christoph Haas <[EMAIL PROTECTED]> wrote:
The problem has been raised in - http://code.djangoproject.com/ticket/1051
Did anyone else find a workaround? Is it meanwhile possible to use at least a models.py without using "inspectdb"? My experiments with 'schemaname.tablename' just lead me to "public"."schemaname.tablename" which is obviously not what I want. I'd like to hear comments. Or is PostgreSQL an uncommon DBMS to use with Django? (btw, is there a reason to prefer psycopg over psycopg2?) I can of course restrain myself to the "public" schema but my application would benefit from different schemas.
Postgres is the database that is used by most of the core developers, AFAIK (it's certainly my DB of choice, and Jacob has blogged Postgres as his preference in the past). The only reason to prefer psycopg over psycopg2 is historical - the API for psycopg2 wasn't finalized until quite recently, so we didn't recommend using it. However, the psycopg backend has a few problems with unicode, so I suspect the official line may soon switch to 'use v2' (probably before Django goes v1.0). Regarding schema - I can't think of any fundamental objection to including them, other than whatever method is used must degrade gracefully to the other DB backends. The reason that ticket #1051 hasn't received any attention is because it simply isn't a priority for the core developers. Personally, I've never had a Django-related application where namespacing became anything close to a problem requiring a solution. However, if someone were to do a good triage job (see the docs for what this means - and for the record, this would constitute a 'big change'), and the required changes degraded gracefully to the other backends, and there was documentation, and there were tests exercising the functinoality, I don't see any reason that support for Postgres schemas couldn't be included. 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
