#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 anonymous):
Replying to [comment:7 crippledcanary]:
> I don't have time to fix this right now... Better someone else does it.
Fixing this should change all the logic at
{{{django.db.backends.create_test_db}}}, as for MySQL schemas are not
really schemas, but databases - therefore, there should be not one, but
several {{{test_*}}} databases.
I'm interested in fixing this so schema support can be checked in (really
needed on PostgreSQL), but want feedback from MySQL users.
So, are MySQL databases really equivalents of schemas? If databases are
like schemas, it would need to patch model's db_schemas to
{{{test_schemaname}}} while testing. I don't like the idea of
monkeypatching names for tests, as custom SQL will fail with different
"schema" (not really) names. Isn't cleaner to fallback to less features
for MySQL (as we do for SQLite)?
--
Ticket URL: <http://code.djangoproject.com/ticket/6148#comment:16>
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
-~----------~----~----~----~------~----~------~--~---
