Opened 19 years ago
Last modified 17 years ago
#87 closed enhancement
Oracle database support. — at Initial Version
| Reported by: | Owned by: | Adrian Holovaty | |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | |
| Severity: | normal | Keywords: | oracle database db sequence |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | UI/UX: |
Description
From django-irc:
jrhuggins: "adrian_h, I looked into how Oracle support would work for Django... it would also require "django\bin\django-admin.py"
adrian_h :jrhuggins: Which changes would need to be made to django-admin?
jrhuggins: because auto-increment requires a separate "create sequence" statement next to your create table and drop table statements.
jrhuggins: and those statements live in django-admin...
adrian_h: ah
jrhuggins: needs to be refactored..
adrian_h: Shouldn't be too difficult to refactor
jrhuggins: maxDB (SAP's db) does the same thing
jrhuggins: any objections to making the "CREATE table (and sequence)" overridable by the db-specific drivers?
adrian_h: No objections at all
jrhuggins: I'll open a ticket for it... then start to think about possible patches..