| 1 | | From django-irc: |
| 2 | | |
| 3 | | '''jrhuggins''': "adrian_h, I looked into how Oracle support would work for Django... it would also require "django\bin\django-admin.py" |
| 4 | | |
| 5 | | '''adrian_h''' :jrhuggins: Which changes would need to be made to django-admin? |
| 6 | | |
| 7 | | '''jrhuggins''': because auto-increment requires a separate "create sequence" statement next to your create table and drop table statements. |
| 8 | | |
| 9 | | '''jrhuggins''': and those statements live in django-admin... |
| 10 | | |
| 11 | | '''adrian_h''': ah |
| 12 | | |
| 13 | | '''jrhuggins''': needs to be refactored.. |
| 14 | | |
| 15 | | '''adrian_h''': Shouldn't be too difficult to refactor |
| 16 | | |
| 17 | | '''jrhuggins''': maxDB (SAP's db) does the same thing |
| 18 | | |
| 19 | | '''jrhuggins''': any objections to making the "CREATE table (and sequence)" overridable by the db-specific drivers? |
| 20 | | |
| 21 | | '''adrian_h''': No objections at all |
| 22 | | |
| 23 | | '''jrhuggins''': I'll open a ticket for it... then start to think about possible patches.. |
| | 1 | Here's a patch for Oracle support. |