| 185 | |
| 186 | === Improving the less popular database backends === |
| 187 | * '''Complexity:''' Medium |
| 188 | |
| 189 | Django supports several database backends, but not equally. The less popular backends -- Oracle in core, as well as open-source backends outside core, could probably use some love. As an example, Oracle has three major problems: |
| 190 | |
| 191 | * The GIS backend is broken (it does not pass Django's own test-suite) |
| 192 | * Python 3 is [ticket:20725 not supported] (this is a problem with the Python driver, requiring C programming) |
| 193 | * The handling of case in database object names is problematic (e.g. #20487) |
| 194 | |
| 195 | While these alone would not fill an agenda for a full GSoC project, an interested student could collect enough related issues -- perhaps in more than one backend -- to keep busy for the whole term. |
| 196 | |
| 197 | Keep in mind that for working on 3rd-party backends, a committer for the relevant backend will probably need to be involved in mentoring; however, given such involvement, Django will accept such GSoC projects. |
| 198 | |
| 199 | See also: |
| 200 | |
| 201 | * [https://code.djangoproject.com/query?status=assigned&status=new&summary=~oracle&or&status=assigned&status=new&keywords=~oracle&col=id&col=summary&col=status&col=owner&col=type&col=component&order=priority Trac's list of Oracle issues] |
| 202 | * Similar queries for 3rd-party backends should be added here |