#1051: [patch] Add support for PostgreSQL Schemas
-------------------------------------------------+--------------------------
Reporter: Mao Xizeng <[EMAIL PROTECTED]> | Owner: adrian
Status: new | Component:
Database wrapper
Version: SVN | Resolution:
Keywords: PostgreSQL Schemas | Stage:
Design decision needed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 1 | Needs_better_patch: 1
-------------------------------------------------+--------------------------
Comment (by Birju Prajapati):
Issues with the search path route:[[BR]]
1. When there are two tables of the same name in different schemas you
wont be able to access the table later in the search path.[[BR]]
2. If you have many apps in one project, importing a model that is in a
separate app into the 'current' one could mean that the entire search path
chain may have to be searched.[[BR]]
I'm not a fan of the project-wide search path as it seems redundant: you
can set up a user in Postgres that Django uses and have that user set up
using
{{{
'ALTER USER BLAH SET SEARCH PATH = ....'
}}}
What are the issues in using the db_table meta options by explicitly
specifying 'schema.table' and not quoting the first '.' wrt to some
setting?
--
Ticket URL: <http://code.djangoproject.com/ticket/1051#comment:12>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
