#6148: Add generic support for database schemas
---------------------------------------------------+------------------------
Reporter: ikelly | Owner: kmpm
Status: assigned | 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 ramiro):
Last patch (`generic-db_schema-r11871.diff`) when applied to the exact
revisio it was generatd against, gives the following results:
* sqlite3 (patch should be a noop): 21 failures, 12 errors of 1171 tests
* PostgreSQL (8.3): 21 failures, 13 errors of 1172 tests
I've been working on this and reached the following state:
1. Updated the patch to the last revision in Django trunk just before the
multi-db landing: r11951.
2. Fixed several bugs so the Django test suite runs on both PostgreSQL
and sqlite3 without any error introduced by the patch.
See `6148-generic-schema-support-r11951.diff` (download it to be able to
review it).
I believe the next steps needed would be:
* Test against MySQL and Oracle and fix any problems so they also reach
zero errors.
* Add more tests?
* Port to trunk as of now (post multi-db), hopefully we will be able to
do that in the feature freeze period after 1.2beta1
IMHO if we do the effort on this we can provide a working patch against
1.2 so testers can play and report back w/o much trouble and then aim for
inclusion in Django 1.3.
--
Ticket URL: <http://code.djangoproject.com/ticket/6148#comment:54>
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.
