From: Dan S. <de...@gm...> - 2005-01-29 20:24:43
|
Hi Yuval, Man-Yong: Any chance of that 1.0 release happening? Also, it would be a really nice follow-up if Man-Yong could produce the win32 binaries for the relatively recent Python 2.4 release. When you start developing the 1.1 branch, would you consider instituting a basic Contributor License Agreement (CLA) like Eclipse and Apache do? The CLA is a legal process that asks would-be contributors & the contributors' employers to sign off on a form stating that the code they are contributing is rightfully theirs to contribute -- basically a way of avoiding any contributions from shady sources. My employer is a bit wary of projects that don't hava a CLA process, so I can't be too useful to the effort without it :( Unless you call sending requests and little reminder notes to the mailing list useful... Dan On Thu, 20 Jan 2005 17:51:38 +0200, Yuval Turgeman <yu...@ad...> wrote: > Dan Scott wrote: > > >Sounds like a good basis for a 1.0 release! > > > >The only thing that confuses me with the current release is exception > >handling; the Python DB-API 2.0 documents a fairly clean hierarchy of > >exceptions and warnings, but I've never been able to catch one of > >those exceptions (_db2.error). Maybe it's just me :) > > > > > Hehe... it's not just you, the current error handling is far from being > complete... my favorite is "an error occurred but I dont know why" ;-) > > >That might be an interesting direction to explore. I'm a little > >worried that the performance would suffer in comparison to a native > >implementation based on SQLPrepare() / SQLExecute() / SQLFetchScroll() > >-- but hey, the proof is always in the code :) > > > > > We would still use those functions (I think we have to, according to the > Db2 api). The only difference is that we'll have a connection object > which implements a "query()" method, which does the actual query (using > the functions you mentioned), and a result object, exactly like MySQLdb > (i really it)... that's at least what I had in mind... :) > > >There have been no major changes in the DB2 CLI API in V8.2 that I'm > >aware of; that API tends to stay pretty stable. The minor changes to > >the API documentation for V8.2 have been marked with a 7 in the > >left-hand margin in the DB2 Information Center: for example, > >SQLConnect(): http://publib.boulder.ibm.com/infocenter/db2help/topic/com.ibm.db2.udb.doc/ad/r0000575.htm > > > > > Cool, I'll read about it a little also. > > Thanks! > > -- > Yuval Turgeman > Content Technology, Aduva LTD. > > |