Opened 17 years ago
Closed 16 years ago
#5052 closed (wontfix)
Backend for DB2 v9 database
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Keywords: | DB2 | |
| Cc: | mateusz@… | Triage Stage: | Design decision needed |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | yes |
| Easy pickings: | no | UI/UX: | no |
Description
This patch adds support for a IBM DB2 v9 database (including the free DB2 Express C version).
There are still a number of issues, see the base.py file for details.
Attachments (5)
Change History (11)
by , 17 years ago
| Attachment: | db2_9.patch added |
|---|
comment:1 by , 17 years ago
I think you reversed the patch filenames, there should be a '+' in front of new lines, not a '-' ;-)
comment:2 by , 17 years ago
Bummer, should have checked, always seem to get the order of these things wrong.
Added a new version.
Thanks,
Koen
comment:3 by , 17 years ago
| Patch needs improvement: | set |
|---|---|
| Triage Stage: | Unreviewed → Design decision needed |
I can't really triage this since I don't have much knowledge about db2. A few random remarks (and don't take my word as final authority)
- runshell() needs to set up the environment so that db2 connects to the right database etc.
- class Cursor: you probably shouldn't use iso-8859-1 as default charset. It looks so ... arbitrary. UTF-8 is kind of standard in Django.
- class DB2QuerySet: It looks weird to me that you have to overwrite _get_sql_clause, and it would be bad for maintenance.
In order to get this patch into Django, youl'll probably need to find more people to support it. Post a note on django-users, in case you haven't already.
I set the triage state to "decision needed" because the integration of new backends always needs the approval of the core developers.
by , 17 years ago
| Attachment: | db2_9_6110.diff added |
|---|
patch against trunk r6110, still a lot issues left though
by , 17 years ago
| Attachment: | pydb2-db2backend.zip added |
|---|
a DB2 backend compatible with 6399 revision and a modified version of PyDB2
by , 17 years ago
| Attachment: | db2_9_6600.diff added |
|---|
A new version of the db2 9 backend. Some Oracle code has been reactivated.
comment:4 by , 17 years ago
| Cc: | added |
|---|
comment:5 by , 17 years ago
Please check this ticket:
and following links:
- http://groups.google.com/group/ibm_db/browse_thread/thread/18d3eec89eca7e7b
- http://code.google.com/p/ibm-db/
- http://antoniocangiano.com/2007/09/04/python-django-and-db2-status-update/
- http://antoniocangiano.com/2008/02/13/ibm-releases-db2-adapter-for-sqlalchemy/
- http://antoniocangiano.com/2007/09/19/db2-on-mac/
comment:6 by , 16 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
New database backends should be maintained out of tree for a while first before being proposed for inclusion. We want to see that there's a healthy userbase and maintenance record before putting something into core. So please create an external project for this (e.g. at google-code). If changes are needed to core, most likely in the area of adding extra DatabaseOperation or DatabaseFeature entries, certainly create a patch or discuss the ideas on django-dev. We're happy to make it easy for people to have external database backends, but we've been bitten before with including external backends too fast and prefer to make it easy for us and the maintainers not to have to do so.
DB2 backend