Opened 15 years ago
Last modified 13 years ago
#11706 closed
Use of RETURNING means Oracle 9i is no longer supported — at Initial Version
| Reported by: | Matt Boersma | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 1.1 |
| Severity: | Keywords: | Oracle oracle RETURNING | |
| Cc: | Erin Kelly | Triage Stage: | Accepted |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
See closed ticket #10473. The "RETURNING...INTO" SQL construct is supported only in Oracle 10g and later, so effectively Django 1.1 will no longer work on Oracle 9i because INSERT statements will fail with "ORA-22816: unsupported feature with RETURNING clause."
Oracle 9i is quite old and no longer actively sold or available for download from www.oracle.com (11gR1 is current). However, if you know Oracle shops, they aren't often aggressive about upgrading--where Ian and I happen to work is one example of this. So I see three solutions:
1) Fall back to the old, compatible code that didn't use RETURNING
2) Make the use of RETURNING optional, conditional on server version
3) Correct the docs to say that Oracle 10g and later are supported in Django 1.1