Menu
▾
▴
pydb2-discuss
|
From: Dan S. <de...@gm...> - 2005-01-20 02:34:50
|
Patrick et al: I just wanted to request that the code in CVS HEAD be released as a formal point release for pyDB2. The 0.996a release is so unstable that it's almost unusable, but the latest code in CVS cleans up the segfault conditions I had been running into in my tests. This would also bring the source code release closer to being in line with the Windows binary build hosted on Man-Yong Lee's FTP site (which is listed as 0.998). Dan |
|
From: Patrick K. O'B. <po...@or...> - 2005-01-20 03:02:26
|
Dan Scott wrote: > Patrick et al: > > I just wanted to request that the code in CVS HEAD be released as a > formal point release for pyDB2. The 0.996a release is so unstable that > it's almost unusable, but the latest code in CVS cleans up the > segfault conditions I had been running into in my tests. > > This would also bring the source code release closer to being in line > with the Windows binary build hosted on Man-Yong Lee's FTP site (which > is listed as 0.998). I'm more than happy to give anyone who volunteers access to the CVS repository and SourceForge tools so that a formal release can be made. Since I'm not actively using DB2, I'd rather someone else step forward. If you would like to volunteer, just give me your SourceForge account name and I'll set you up. Anyone? -- Patrick K. O'Brien Orbtech http://www.orbtech.com Schevo http://www.schevo.org Pypersyst http://www.pypersyst.org |
|
From: Yuval T. <yu...@ad...> - 2005-01-20 09:22:59
|
Patrick K. O'Brien wrote: > Dan Scott wrote: > >> Patrick et al: >> >> I just wanted to request that the code in CVS HEAD be released as a >> formal point release for pyDB2. The 0.996a release is so unstable that >> it's almost unusable, but the latest code in CVS cleans up the >> segfault conditions I had been running into in my tests. >> >> This would also bring the source code release closer to being in line >> with the Windows binary build hosted on Man-Yong Lee's FTP site (which >> is listed as 0.998). > > > I'm more than happy to give anyone who volunteers access to the CVS > repository and SourceForge tools so that a formal release can be made. > Since I'm not actively using DB2, I'd rather someone else step > forward. If you would like to volunteer, just give me your > SourceForge account name and I'll set you up. Anyone? > I also think it's about time we release a new version... I wouldn't mind doing that (you already gave me release privileges). -- Yuval Turgeman Content Technology, Aduva LTD. |
|
From: ??? <yo...@li...> - 2005-01-20 10:07:31
|
SGkNCg0KLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSANCkZyb206ICJZdXZhbCBUdXJnZW1h biIgPHl1dmFsQGFkdXZhLmNvbT4NClRvOiAiUGF0cmljayBLLiBPJ0JyaWVuIiA8cG9icmllbkBv cmJ0ZWNoLmNvbT4NCkNjOiAiRGFuIFNjb3R0IiA8ZGVuaWFsc0BnbWFpbC5jb20+OyA8cHlkYjIt ZGlzY3Vzc0BsaXN0cy5zb3VyY2Vmb3JnZS5uZXQ+DQpTZW50OiBUaHVyc2RheSwgSmFudWFyeSAy MCwgMjAwNSA2OjI0IFBNDQpTdWJqZWN0OiBSZTogW1B5REIyLWRpc2N1c3NdIE5ldyByZWxlYXNl IG9uIHNvdXJjZWZvcmdlPw0KDQoNCj4+DQo+PiBJJ20gbW9yZSB0aGFuIGhhcHB5IHRvIGdpdmUg YW55b25lIHdobyB2b2x1bnRlZXJzIGFjY2VzcyB0byB0aGUgQ1ZTIA0KPj4gcmVwb3NpdG9yeSBh bmQgU291cmNlRm9yZ2UgdG9vbHMgc28gdGhhdCBhIGZvcm1hbCByZWxlYXNlIGNhbiBiZSBtYWRl LiANCj4+IFNpbmNlIEknbSBub3QgYWN0aXZlbHkgdXNpbmcgREIyLCBJJ2QgcmF0aGVyIHNvbWVv bmUgZWxzZSBzdGVwIA0KPj4gZm9yd2FyZC4gIElmIHlvdSB3b3VsZCBsaWtlIHRvIHZvbHVudGVl ciwganVzdCBnaXZlIG1lIHlvdXIgDQo+PiBTb3VyY2VGb3JnZSBhY2NvdW50IG5hbWUgYW5kIEkn bGwgc2V0IHlvdSB1cC4gIEFueW9uZT8NCj4+DQo+IEkgYWxzbyB0aGluayBpdCdzIGFib3V0IHRp bWUgd2UgcmVsZWFzZSBhIG5ldyB2ZXJzaW9uLi4uIEkgd291bGRuJ3QgbWluZCANCj4gZG9pbmcg dGhhdCAoeW91IGFscmVhZHkgZ2F2ZSBtZSByZWxlYXNlIHByaXZpbGVnZXMpLg0KPiANCg0KSSBh Z3JlZSB3aXRoIHlvdSwgWXV2YWwuICBJIHRoaW5rIHdlIHNob3VsZCByZWxlYXNlIHRoZSBjdXJy ZW50IENWUyBhcyB2MS4wIChzdGFibGU/KQ0KYW5kIHN0YXJ0IGEgbmV3IGJyYW5jaCBhcyB2MS4x IChkZXZlbG9wbWVudCB2ZXJzaW9uKQ0KDQpZdXZhbCwgaGF2ZSB5b3Ugc3RhcnRlZCBhIG5ldyBk YjIgbW9kdWxlIGNvZGluZyBvciBoYXZlIGFueSBpZGVhIHdoYXQgYSBuZXcgZGIyIG1vZHVsZQ0K c2hvdWxkIGJlPw0KDQpJJ20gc2V0dGluZyB1cCBEQjIgdjguMiBzeXN0ZW0gcmlnaHQgbm93Lg0K DQo= |
|
From: Yuval T. <yu...@ad...> - 2005-01-20 11:50:34
|
Hello, >I agree with you, Yuval. I think we should release the current CVS as v1.0 (stable?) >and start a new branch as v1.1 (development version) > > What we have until now is pretty stable (AFAIK). All the (known) bugs are fixed (segfaults, leaks, etc.). So, yeah we could release it as 1.0 and start working on the next generation, making sure it's fully compliant with python's DB-API (i'm not sure the current module is fully compliant). >Yuval, have you started a new db2 module coding or have any idea what a new db2 module >should be? > > Yes, I have, actually... I started implementing a MySQLdb-like module, which means implementing the basics in C (connection object, errors) and all the rest (connection object wrappers, cursors, converters, etc.) in python. This would help us with all the ref. counting problems we had in the past (like the problem we had with the cyclic dep. between the cursor object and connection object for example). >I'm setting up DB2 v8.2 system right now. > > Any changes in the DB2 API for 8.2 ? -- Yuval Turgeman Content Technology, Aduva LTD. |
|
From: Yuval T. <yu...@ad...> - 2005-01-20 15:50:06
|
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. |
|
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. > > |
|
From: ??? <yo...@li...> - 2005-01-31 08:12:21
|
SGkgRGFuLA0KDQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogIkRhbiBTY290 dCIgPGRlbmlhbHNAZ21haWwuY29tPg0KVG86IDxweWRiMi1kaXNjdXNzQGxpc3RzLnNvdXJjZWZv cmdlLm5ldD4NClNlbnQ6IFN1bmRheSwgSmFudWFyeSAzMCwgMjAwNSA1OjI0IEFNDQpTdWJqZWN0 OiBSZTogW1B5REIyLWRpc2N1c3NdIE5ldyByZWxlYXNlIG9uIHNvdXJjZWZvcmdlPw0KDQoNCj4g SGkgWXV2YWwsIE1hbi1Zb25nOg0KPiANCj4gQW55IGNoYW5jZSBvZiB0aGF0IDEuMCByZWxlYXNl IGhhcHBlbmluZz8NCg0KWXV2YWwsIEkgd2FudCB5b3UgdG8gcmVsZWFzZSAxLjAuICBJbiBmYWN0 LCBJIGRvbid0IGtub3cgaG93IHRvIHJlbGVhc2UgYSBuZXcgdmVyc2lvbiBpbiBzZi5uZXQuDQoN Cj4gQWxzbywgaXQgd291bGQgYmUgYSByZWFsbHkgbmljZSBmb2xsb3ctdXAgaWYgTWFuLVlvbmcg Y291bGQgcHJvZHVjZQ0KPiB0aGUgd2luMzIgYmluYXJpZXMgZm9yIHRoZSByZWxhdGl2ZWx5IHJl Y2VudCBQeXRob24gMi40IHJlbGVhc2UuDQoNClN1cmUuDQoNCj4gV2hlbiB5b3Ugc3RhcnQgZGV2 ZWxvcGluZyB0aGUgMS4xIGJyYW5jaCwgd291bGQgeW91IGNvbnNpZGVyDQo+IGluc3RpdHV0aW5n IGEgYmFzaWMgQ29udHJpYnV0b3IgTGljZW5zZSBBZ3JlZW1lbnQgKENMQSkgbGlrZSBFY2xpcHNl DQo+IGFuZCBBcGFjaGUgZG8/IFRoZSBDTEEgaXMgYSBsZWdhbCBwcm9jZXNzIHRoYXQgYXNrcyB3 b3VsZC1iZQ0KPiBjb250cmlidXRvcnMgJiB0aGUgY29udHJpYnV0b3JzJyBlbXBsb3llcnMgdG8g c2lnbiBvZmYgb24gYSBmb3JtDQo+IHN0YXRpbmcgdGhhdCB0aGUgY29kZSB0aGV5IGFyZSBjb250 cmlidXRpbmcgaXMgcmlnaHRmdWxseSB0aGVpcnMgdG8NCj4gY29udHJpYnV0ZSAtLSBiYXNpY2Fs bHkgYSB3YXkgb2YgYXZvaWRpbmcgYW55IGNvbnRyaWJ1dGlvbnMgZnJvbSBzaGFkeQ0KPiBzb3Vy Y2VzLg0KPiANCj4gTXkgZW1wbG95ZXIgaXMgYSBiaXQgd2FyeSBvZiBwcm9qZWN0cyB0aGF0IGRv bid0IGhhdmEgYSBDTEEgcHJvY2VzcywNCj4gc28gSSBjYW4ndCBiZSB0b28gdXNlZnVsIHRvIHRo ZSBlZmZvcnQgd2l0aG91dCBpdCA6KCBVbmxlc3MgeW91IGNhbGwNCj4gc2VuZGluZyByZXF1ZXN0 cyBhbmQgbGl0dGxlIHJlbWluZGVyIG5vdGVzIHRvIHRoZSBtYWlsaW5nIGxpc3QNCj4gdXNlZnVs Li4uDQo+IA0KPiBEYW4NCg0KT2YgY291cnNlIQ0KDQpIYXZlIGEgbmljZSBkYXl+DQo= |
|
From: Dan S. <de...@gm...> - 2005-01-31 21:21:08
|
On Mon, 31 Jan 2005 17:12:00 +0900, ??? <yo...@li...> wrote: > Hi Dan, > > ----- Original Message ----- > From: "Dan Scott" <de...@gm...> > To: <pyd...@li...> > Sent: Sunday, January 30, 2005 5:24 AM > Subject: Re: [PyDB2-discuss] New release on sourceforge? > > > > Hi Yuval, Man-Yong: > > > > Any chance of that 1.0 release happening? > > Yuval, I want you to release 1.0. In fact, I don't know how to release a new version in sf.net. Yuval, when you create the release, let me know and I'll update the Python Package Index entry for the project. > > 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. > > Sure. Excellent! > > 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 > > Of course! That's great! For further information on the Contributor Licensing Agreement (Python itself adopted a CLA process earlier this month) you can look at http://www.python.org/psf/contrib.html This is really exciting; with these steps in place I think this project will really take off and become more active again. |
|
From: ??? <yo...@li...> - 2005-03-08 12:29:24
|
SGl+IGV2ZXJ5b25lLA0KDQpJJ3ZlIGp1c3QgcmVmYWN0b3JlZCB0aGUgbW9kdWxlIGFuZCB1cGxv YWRlZCB0byBmdHA6Ly9wZW9wbGUubGludXhrb3JlYS5jby5rci9wdWIvREIyL3NyYy4NCkNhbiB5 b3UgcGxlYXNlIHJldmlldyB0aGUgc291cmNlIGNvZGU/DQoNCkknbSBzdXJlIHRoYXQgdGhpcyB2 ZXJzaW9uIGlzIG11Y2ggYmV0dGVyIHRoYW4gdGhlIHByZXZpb3VzIG9uZS4NCkl0IGluY2x1ZGVz IHVuaXR0ZXN0IGNvZGUgbm93Lg0KDQpTb29uZXIgb3IgbGF0ZXIsIEkgd291bGQgbGlrZSB0byB1 cGxvYWQgdGhpcyB2ZXJzaW9uIHRvIHNmLm5ldC4NCg0KLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAt LS0tLSANCkZyb206ICJEYW4gU2NvdHQiIDxkZW5pYWxzQGdtYWlsLmNvbT4NClRvOiA8cHlkYjIt ZGlzY3Vzc0BsaXN0cy5zb3VyY2Vmb3JnZS5uZXQ+DQpTZW50OiBUdWVzZGF5LCBGZWJydWFyeSAw MSwgMjAwNSA2OjIwIEFNDQpTdWJqZWN0OiBSZTogW1B5REIyLWRpc2N1c3NdIE5ldyByZWxlYXNl IG9uIHNvdXJjZWZvcmdlPw0KDQoNCj4gT24gTW9uLCAzMSBKYW4gMjAwNSAxNzoxMjowMCArMDkw MCwgPz8/IDx5b25nQGxpbnV4a29yZWEuY28ua3I+IHdyb3RlOg0KPj4gSGkgRGFuLA0KPj4gDQo+ PiAtLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tDQo+PiBGcm9tOiAiRGFuIFNjb3R0IiA8ZGVu aWFsc0BnbWFpbC5jb20+DQo+PiBUbzogPHB5ZGIyLWRpc2N1c3NAbGlzdHMuc291cmNlZm9yZ2Uu bmV0Pg0KPj4gU2VudDogU3VuZGF5LCBKYW51YXJ5IDMwLCAyMDA1IDU6MjQgQU0NCj4+IFN1Ympl Y3Q6IFJlOiBbUHlEQjItZGlzY3Vzc10gTmV3IHJlbGVhc2Ugb24gc291cmNlZm9yZ2U/DQo+PiAN Cj4+IA0KPj4gPiBIaSBZdXZhbCwgTWFuLVlvbmc6DQo+PiA+DQo+PiA+IEFueSBjaGFuY2Ugb2Yg dGhhdCAxLjAgcmVsZWFzZSBoYXBwZW5pbmc/DQo+PiANCj4+IFl1dmFsLCBJIHdhbnQgeW91IHRv IHJlbGVhc2UgMS4wLiAgSW4gZmFjdCwgSSBkb24ndCBrbm93IGhvdyB0byByZWxlYXNlIGEgbmV3 IHZlcnNpb24gaW4gc2YubmV0Lg0KPiANCj4gWXV2YWwsIHdoZW4geW91IGNyZWF0ZSB0aGUgcmVs ZWFzZSwgbGV0IG1lIGtub3cgYW5kIEknbGwgdXBkYXRlIHRoZQ0KPiBQeXRob24gUGFja2FnZSBJ bmRleCBlbnRyeSBmb3IgdGhlIHByb2plY3QuDQo+IA0KPj4gPiBBbHNvLCBpdCB3b3VsZCBiZSBh IHJlYWxseSBuaWNlIGZvbGxvdy11cCBpZiBNYW4tWW9uZyBjb3VsZCBwcm9kdWNlDQo+PiA+IHRo ZSB3aW4zMiBiaW5hcmllcyBmb3IgdGhlIHJlbGF0aXZlbHkgcmVjZW50IFB5dGhvbiAyLjQgcmVs ZWFzZS4NCj4+IA0KPj4gU3VyZS4NCj4gDQo+IEV4Y2VsbGVudCENCj4gDQo+PiA+IFdoZW4geW91 IHN0YXJ0IGRldmVsb3BpbmcgdGhlIDEuMSBicmFuY2gsIHdvdWxkIHlvdSBjb25zaWRlcg0KPj4g PiBpbnN0aXR1dGluZyBhIGJhc2ljIENvbnRyaWJ1dG9yIExpY2Vuc2UgQWdyZWVtZW50IChDTEEp IGxpa2UgRWNsaXBzZQ0KPj4gPiBhbmQgQXBhY2hlIGRvPyBUaGUgQ0xBIGlzIGEgbGVnYWwgcHJv Y2VzcyB0aGF0IGFza3Mgd291bGQtYmUNCj4+ID4gY29udHJpYnV0b3JzICYgdGhlIGNvbnRyaWJ1 dG9ycycgZW1wbG95ZXJzIHRvIHNpZ24gb2ZmIG9uIGEgZm9ybQ0KPj4gPiBzdGF0aW5nIHRoYXQg dGhlIGNvZGUgdGhleSBhcmUgY29udHJpYnV0aW5nIGlzIHJpZ2h0ZnVsbHkgdGhlaXJzIHRvDQo+ PiA+IGNvbnRyaWJ1dGUgLS0gYmFzaWNhbGx5IGEgd2F5IG9mIGF2b2lkaW5nIGFueSBjb250cmli dXRpb25zIGZyb20gc2hhZHkNCj4+ID4gc291cmNlcy4NCj4+ID4NCj4+ID4gTXkgZW1wbG95ZXIg aXMgYSBiaXQgd2FyeSBvZiBwcm9qZWN0cyB0aGF0IGRvbid0IGhhdmEgYSBDTEEgcHJvY2VzcywN Cj4+ID4gc28gSSBjYW4ndCBiZSB0b28gdXNlZnVsIHRvIHRoZSBlZmZvcnQgd2l0aG91dCBpdCA6 KCBVbmxlc3MgeW91IGNhbGwNCj4+ID4gc2VuZGluZyByZXF1ZXN0cyBhbmQgbGl0dGxlIHJlbWlu ZGVyIG5vdGVzIHRvIHRoZSBtYWlsaW5nIGxpc3QNCj4+ID4gdXNlZnVsLi4uDQo+PiA+DQo+PiA+ IERhbg0KPj4gDQo+PiBPZiBjb3Vyc2UhDQo+IA0KPiBUaGF0J3MgZ3JlYXQhIEZvciBmdXJ0aGVy IGluZm9ybWF0aW9uIG9uIHRoZSBDb250cmlidXRvciBMaWNlbnNpbmcNCj4gQWdyZWVtZW50IChQ eXRob24gaXRzZWxmIGFkb3B0ZWQgYSBDTEEgcHJvY2VzcyBlYXJsaWVyIHRoaXMgbW9udGgpIHlv dQ0KPiBjYW4gbG9vayBhdCBodHRwOi8vd3d3LnB5dGhvbi5vcmcvcHNmL2NvbnRyaWIuaHRtbA0K PiANCj4gVGhpcyBpcyByZWFsbHkgZXhjaXRpbmc7IHdpdGggdGhlc2Ugc3RlcHMgaW4gcGxhY2Ug SSB0aGluayB0aGlzDQo+IHByb2plY3Qgd2lsbCByZWFsbHkgdGFrZSBvZmYgYW5kIGJlY29tZSBt b3JlIGFjdGl2ZSBhZ2Fpbi4NCj4gDQo+IA0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+IFRoaXMgU0YuTmV0IGVtYWlsIGlzIHNwb25z b3JlZCBieTogSW50ZWxsaVZJRVcgLS0gSW50ZXJhY3RpdmUgUmVwb3J0aW5nDQo+IFRvb2wgZm9y IG9wZW4gc291cmNlIGRhdGFiYXNlcy4gQ3JlYXRlIGRyYWctJi1kcm9wIHJlcG9ydHMuIFNhdmUg dGltZQ0KPiBieSBvdmVyIDc1JSEgUHVibGlzaCByZXBvcnRzIG9uIHRoZSB3ZWIuIEV4cG9ydCB0 byBET0MsIFhMUywgUlRGLCBldGMuDQo+IERvd25sb2FkIGEgRlJFRSBjb3B5IGF0IGh0dHA6Ly93 d3cuaW50ZWxsaXZpZXcuY29tL2dvL29zZG5fbmwNCj4gX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX18NCj4gUHlEQjItZGlzY3VzcyBtYWlsaW5nIGxpc3QNCj4g UHlEQjItZGlzY3Vzc0BsaXN0cy5zb3VyY2Vmb3JnZS5uZXQNCj4gaHR0cHM6Ly9saXN0cy5zb3Vy Y2Vmb3JnZS5uZXQvbGlzdHMvbGlzdGluZm8vcHlkYjItZGlzY3Vzcw0KPg== |
|
From: Yuval T. <yu...@ad...> - 2005-07-11 08:16:42
|
??? wrote: >Hi~ everyone, > >I've just refactored the module and uploaded to ftp://people.linuxkorea.co.kr/pub/DB2/src. >Can you please review the source code? > >I'm sure that this version is much better than the previous one. >It includes unittest code now. > >Sooner or later, I would like to upload this version to sf.net. > > This looks like a very nice release! Here's a list of non-standard features I was using in the previous module that have changed (and broke my code) :) 1. Connection object: removed .autocommit() function (Python DB API: constructor kwarg "autoCommit" for db specific parameters). 2. Missing DB2.CLOB type (Python DB API: describing very large columns should be done using DB2.Binary). 3. Fetchone returns a list rather than a tuple (Python DB API: "fetchone()" returns a sequence) I didn't have much time to dedicate for this project lately (sorry)... I am just starting to test the new module now. It looks very promising, I'll tell you how it goes. Thanks, -- Yuval Turgeman Content Technology, Aduva LTD. |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X