Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#6995 closed (wontfix)

Db2 adapter - another implementation (first is #5052)

Reported by: trebor74hr@… Owned by: nobody
Component: Database layer (models, ORM) Version: 0.96
Severity: Keywords: db2
Cc: Triage Stage: Unreviewed
Has patch: yes Needs documentation: yes
Needs tests: yes Patch needs improvement: yes
Easy pickings: UI/UX:

Description

(mainly copied from http://code.google.com/p/ibm-db/issues/detail?id=10)

I was inspired by this thread:

so I send you Django adapter (alpha) based on PyDB2.

This is based on Django 0.96 release. I needed django working on db2 and did adapter by looking at code of other adapters. Module is functional in my environment, but ... Didn't runned django tests against db2 module, so probably lot of problems still exist.

In attachment you'll find:

  • db2 folder from django.db.backends folder
  • django_db2_adapter_0.96.diff - diff agains slightly modified django 0.96 release

I tried to put this ticket content as comment to ticket #5052, but it reported constantly that I'm sending spam. So I decided to open new ticket, you can merge these two tickets if you like.

It would be great all these efforts (ibm_db, #5052, this ticket) can be unified and that all of us can get one good and official django db2 adapter.

Attachments (1)

django_db2_adapter_0.96.zip (30.2 KB) - added by Robert <trebor74hr@…> 8 years ago.
db2 adapter

Download all attachments as: .zip

Change History (5)

comment:1 Changed 8 years ago by Robert <trebor74hr@…>

Component: UncategorizedDatabase wrapper
Has patch: set
Keywords: db2 added
Needs documentation: set
Needs tests: set
Patch needs improvement: set
Version: SVN0.96

Changed 8 years ago by Robert <trebor74hr@…>

Attachment: django_db2_adapter_0.96.zip added

db2 adapter

comment:3 Changed 8 years ago by Marc Fargas

Resolution: wontfix
Status: newclosed

It has been stated in django-developers here that database backends should be implemented as an independent project, and when it's seen that those have a commitment than won't leave them abandoned in django it can be proposed to integrate them.

So, you should think about implementing the db2 backend as a separate project like the MS-SQL one, and if it goes well, in some time, you can bring discussion in django-developers to integrate it.

Marking wontfix then.

comment:4 Changed 8 years ago by Robert Lujo

I agree with the resolution, but just as a reference I'll put here a link to the patched pydb2 driver(maybe somebody will need it): http://sourceforge.net/tracker/index.php?func=detail&aid=2151127&group_id=67548&atid=518208
I hope you won't mind this.
Maybe later I'll start django-code project as suggested - will be implemented as separate module - like described here http://www.pointy-stick.com/blog/2007/11/11/django-tip-external-database-backends/.

Note: See TracTickets for help on using tickets.
Back to Top