#6148: Add generic support for database schemas
---------------------------------------------------+------------------------
Reporter: ikelly | Owner:
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords: oracle
postgresql mysql schemas
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
---------------------------------------------------+------------------------
Comment (by oldium):
Replying to [comment:23 ikelly]:
> Since this ticket has been seeing some activity lately, I decided to put
some work in on the patch. The old patch worked by fudging the schema
into the db_table attribute, which is sort of a hack. I've changed it to
combine db_schema and db_table into an entirely new attribute,
qualified_name.
Please have a look at my patch for your patch (applies after you one),
I've found some quotation problems, also the index name in `CREATE INDEX`
in PostgreSQL cannot contain schema name, because the index is always
created in the same schema as the parent table (see
[http://www.postgresql.org/docs/8.2/static/sql-createindex.html 8.2.13
CREATE INDEX]).
--
Ticket URL: <http://code.djangoproject.com/ticket/6148#comment:24>
Django <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
-~----------~----~----~----~------~----~------~--~---
