Comments on: Python, Django and DB2: we need your input!

By: Jonathan

Jonathan — Mon, 30 Nov -0001 00:00:00 +0000

I don’t know python well enough to suggest anything but db2 express-c appears to be a good deal. I must find some time to try it out.

By: dbt

dbt — Mon, 30 Nov -0001 00:00:00 +0000

did you intentionally exclude OpenBSD, NetBSD, FreeBSD and MacOS X?

By: Antonio Cangiano

Antonio Cangiano — Mon, 30 Nov -0001 00:00:00 +0000

@dbt

Unfortunately *BSD and Mac OS X are not supported at the moment.

By: Masklinn

Masklinn — Mon, 30 Nov -0001 00:00:00 +0000

I think that a DBAPI2-compliant driver would be a very good idea indeed.

But as far as Django, even though I do love and use it, I think that you should work on SQLAlchemy support before considering Django.

Work is being done to use SQLAlchemy in Django anyway, so you could very well kill two birds with one stone.

By: anonymous

anonymous — Mon, 30 Nov -0001 00:00:00 +0000

My suggestion: don't target the Django adapter/ORM specifically, target SQLAlchemy so that _all_ web frameworks (Django, Pylons, TG, etc.) can use db2 express-c. The first step would be to create a DB-API compatible library, then code the SQLA adapter (see SQLA's Oracle adapter for example).

By: Kimutaku

Kimutaku — Mon, 30 Nov -0001 00:00:00 +0000

Hey Antonio, by looking at the ruby driver, the approach seems to be using C bindings (complemented with a kind of “db2 client” I suppose).

Do you know if another approach would be considered? I’m thinking in “type 4” drivers for java. It’s way cool in java that you just drop a couple of jars, point to the appropiate url and the app just works. No client needed. That could even help in case of some deployments with a db2 server on linux/windows and django/whathever in another platform.

On the other hand, I assume you know about the python db-sig mailing list (which seems active and healthy) and the pydb2 project.

Anyway, I hope we see an official python-db2 driver anytime soon. You know, the *racle side seems pretty active in the python world, although the existent drivers are non-oficial.

By: Antonio Cangiano

Antonio Cangiano — Mon, 30 Nov -0001 00:00:00 +0000

@Jonathan

It is indeed a good deal, and the best part is that there is no catch.

@Masklinn, @anonymous

I definitely think that implementing an adapter for SQL Alchemy as early as possible is a sound idea.

@Kimutaku

I think the approach that we had in mind was to rely on the DB2 Call Level Interface (CLI) rather than having something similar to the JDBC type 4 driver. However based also on the feedback received, we’ll consider any sensible approach.

Thanks for all the feedback so far, keep it coming. 🙂

By: Vinay Gupta

Vinay Gupta — Mon, 30 Nov -0001 00:00:00 +0000

You might want to talk to the guy who wrote the Python / MySQL driver. He’s very good at what he does, nice to work with (I had some issues and he was very helpful) and it might greatly cut down the learning curve.

By: Antonio Cangiano

Antonio Cangiano — Mon, 30 Nov -0001 00:00:00 +0000

@Vinay Gupta

I won’t be personally writing the driver or the adapter but there will be a dedicated team working on this. Thank you very much for the suggestion though. 🙂

By: tonetheman

tonetheman — Mon, 30 Nov -0001 00:00:00 +0000

Making db express -c slightly easier to download… like actually having the download available instead of the verification might help a bit. [just a suggestion]