Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Django adapter (alpha) based on PyDB2 - contribution #10

Closed
GoogleCodeExporter opened this issue Mar 16, 2015 · 5 comments
Closed

Django adapter (alpha) based on PyDB2 - contribution #10

GoogleCodeExporter opened this issue Mar 16, 2015 · 5 comments
Labels

Comments

@GoogleCodeExporter
Copy link

@GoogleCodeExporter GoogleCodeExporter commented Mar 16, 2015

Hi, 
I was inspired by this thread:
http://groups.google.com/group/ibm_db/browse_thread/thread/18d3eec89eca7e7b
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'm very glad that this project exists, finally python/sqlalchemy have
proper db2 driver. I'm hoping that you'll use this work (or not ;) ), and 
fill the gap for db2-pythonists - django-db2 adapter. Continue with the
good work. 

Regards, 
Robert

Original issue reported on code.google.com by trebor74hr@gmail.com on 9 Apr 2008 at 1:30

Attachments:

@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Mar 16, 2015

I forgot to tell you also to take a look at #5052 Backend for DB2 v9 database
(http://code.djangoproject.com/ticket/5052)

Original comment by trebor74hr@gmail.com on 9 Apr 2008 at 1:36

@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Mar 16, 2015

Robert, as much as we appreciate your willingness to help filling the gap for 
DB2 &
Python/Django enthusiast, this doesn't seem to be a defect you are reporting on
IBM_DB Python driver or DB-API wrapper or SQLAlchemy adapter.

If the PyDB2 driver you mention is the other "Python DB API 2.0 interface to 
IBM's
DB2", then you might want to post this on the SourceForge project: 
http://sourceforge.net/projects/pydb2/

BTW, do you also plan to use/support the ibm_db_dbi (DB-API 2.0 implementation 
based
on ibm_db Python driver) ?

We also need to reiterate the need for Django implementation spec rather than 
code
contributions we cannot take in at this time, due to current legal setup of this
project (a Contribution License Agreement would need to be provided for external
contributions to this project). See how you can help this project in getting 
Django
support:
http://groups.google.com/group/django-developers/browse_frm/thread/80f73f8bbf93c
039?scoring=d&q=ORM&

Original comment by apiti...@ca.ibm.com on 9 Apr 2008 at 2:33

  • Changed state: Invalid
@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Mar 16, 2015

I'm sorry if I was not very clear/correct. it is true that this is not defect, 
and
this is not using ibm_db_dbi module at all, but I was thinking like this: if you
intend to develop db2 django adapter
(http://groups.google.com/group/ibm_db/browse_thread/thread/18d3eec89eca7e7b), 
then
contribution and additional information could help you. 
Partially read the thread, and think that I understand the license problem you
mentioned (IMHO very hard restriction, doesn't sound "open" at all). If this can
help, I'll remove any legal stuff from the code I sent you.

To answer your question, I plan very soon to replace pydb2->ibm_db_dbi in
applications we use, and no, I don't intend to continue development of the code 
I
sent you (django adapter), but if I do, then I'll be looking to use ibm_db_dbi
instead of pydb2.

Hoping that somehow you'll manage to develop good django adapter. Regards.

Original comment by trebor74hr@gmail.com on 9 Apr 2008 at 2:53

@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Mar 16, 2015

Robert, just wanted to clarify, if you read the entire thread referred above, 
it was
never a license issue, the license (Apache) is a standard Open Source one, not 
to
mention that the source code is already out there, as open as you can get:
http://code.google.com/p/ibm-db/source/browse/trunk/IBM_DB/ibm_db_dbi/ibm_db_dbi
.py

The project can be enabled to accept external contributions from Open Source
developers that agree with a Contribution License Agreement (CLA) in order to 
ensure
proper legal requirements. Such CLA is not currently setup for this project, and
until it is available, the team can make use of any public documentation and
developer guides on Django spec, but not actual source code.

Thanks for getting this started.

Original comment by apiti...@ca.ibm.com on 9 Apr 2008 at 6:47

@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Mar 16, 2015

I have added some suggestions/scenario to the thread, please read and post an 
answer
if scenario suites ibm-django developers. Thanks.

Original comment by trebor74hr@gmail.com on 14 Apr 2008 at 9:31

@kadler kadler removed the Priority-Medium label Apr 23, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.