pydb2-discuss — Python DB2 Discussion List

[PyDB2-discuss] Error building PyDB2-1.1.0

[Pratik M. <pm...@ac...>]

Hi,

 

I downloaded and untarred (using Cygwin) PyDB2-1.1.0 available on
Sourceforge on a Windows XP system and then ran 'python setup.py build'

 

I get the following message which is the same as posted on sourceforge bugs
list by someone else a month ago.

 

$ python setup.py build

Your DB2 root is: C:\Program Files\IBM\SQLLIB\

running build

running build_py

running build_ext

building '_db2' extension

C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin\cl.exe /c /nologo
/Ox /MD /W3 /GX /DNDEBUG "-IC:\Program Files\IBM\SQLLIB\include"
-Ic:\Python24\include -Ic:\Python24\PC /Tc_db2_module.c
/Fobuild\temp.win32-2.4\Release\_db2_module.obj

_db2_module.c

_db2_module.c(1855) : error C2036: 'SQLPOINTER' : unknown size

_db2_module.c(2087) : warning C4018: '<' : signed/unsigned mismatch

 

Any ideas as to how to resolve this issue.

 

Best regards,

 

Pratik Mehta

[PyDB2-discuss] pydb2 warnings/errors

[Yuval T. <yu...@ad...>]

Hi,
The new module raises a _db2.Error when the db2 returns SQL0000W
after .execute() (see
http://publib.boulder.ibm.com/infocenter/db2help/index.jsp?topic=/com.ibm.db2.udb.doc/core/rsql0500.htm )

According to the DB2 documentation, codes can end with W, C, and N.
Meaning "Warning or informational messages", "Critical system errors",
and "Error messages (don't know why 'N')"

In the previous versions, this was simply ignored:

    if (rc1 != SQL_NO_DATA && rc1 != SQL_SUCCESS) {
        /* XXX need to cope with SQL_SUCCESS_WITH_INFO */
        return DB2_report_error(self); 
    } ... etc ...

So, since this is a warning, I think the best fix would be to add the
warning to the messages member rather than raising an error.  It's an
easy one to fix:

------------- snip ------------
--- v1.1/_db2_module.c  2005-03-09 03:34:48.000000000 +0200
+++ v1.1-devel/_db2_module.c    2005-07-14 14:19:13.537755000 +0300
@@ -1062,7 +1062,7 @@ DB2CursorObj_execute(DB2CursorObj *self,
 
        if (rc == SQL_SUCCESS) {
                ;
-       } else if (rc == SQL_SUCCESS_WITH_INFO) {
+       } else if (rc == SQL_SUCCESS_WITH_INFO || rc ==
SQL_NO_DATA_FOUND) {
                _DB2CursorObj_fill_Cursor_messages(self);
        } else {
                return _DB2CursorObj_Cursor_Error(self, NULL);
------------- snip ------------

This will append the warning to the cursor.messages:

>>> c.messages 
[(<class _db2.Warning at 0x815c6ac>, ('02000', 100, '[IBM][CLI
Driver][DB2/LINUX
] SQL0100W  No row was found for FETCH, UPDATE or DELETE; or the result
of a que
ry is an empty table.  SQLSTATE=02000\n'))]
>>> 

I think we should set up a nice and simple html site in pydb2.sf.net and
a working cvs...

What do you think?

Thanks,
Yuval.

Re: [PyDB2-discuss] New release on sourceforge?

[Yuval T. <yu...@ad...>]

??? 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.

Re: [PyDB2-discuss] New release on sourceforge?

[Jaco S. <jac...@cl...>]

--- setup.py	2005-06-29 09:32:27.316161600 -0400=0A+++ setup.py.new	2005-07=
-04 18:30:35.035497600 -0400=0A@@ -8,23 +8,23 @@=0A import sys=0A import os=
=0A =0A-# specifiy your DB2 root if auto-find doesn't work=0A+# specify you=
r DB2 root if auto-find doesn't work=0A # (with trailing /)=0A-# ex) DB2=5F=
ROOT =3D "/opt/IBM/db2/V8.1/"=0A-DB2=5FROOT =3D ""=0A+# ex) DB2DIR =3D "/op=
t/IBM/db2/V8.1/"=0A+DB2DIR =3D os.environ['DB2=5FHOME']=0A =0A-def get=5Fdb=
2=5Froot():=0A-	for v in [ '/opt/IBM/db2', '/usr/IBMdb2' ]:=0A+def get=5Fdb=
2=5Froot(dirs =3D [ '/opt/IBM/db2', '/usr/IBMdb2' ]):=0A+	for v in dirs:=0A=
 		if os.path.exists(v):=0A 			files =3D os.listdir(v)=0A 			for vv in file=
s:=0A 				if vv[:1] =3D=3D "V" and vv.find(".") > 0:=0A 					return "%s/%s/=
" % (v, vv)=0A 	else:=0A-		return DB2=5FROOT=0A+		return DB2DIR=0A =0A if s=
ys.platform[:5] =3D=3D 'win32': # Win32=0A-	db2=5Froot=5Fdir =3D 'C:\\Progr=
am Files\\SQLLIB\\'=0A+	db2=5Froot=5Fdir =3D get=5Fdb2=5Froot(['C:/Program =
Files/SQLLIB/'])=0A 	db2lib =3D 'db2cli'=0A else:=0A 	db2=5Froot=5Fdir =3D =
get=5Fdb2=5Froot()=0A=

Re: [PyDB2-discuss] New release on sourceforge?

[Dan S. <de...@gm...>]

Attached is a small patch for setup.py to hopefully improve the build
experience on both Windows and on UNIX (DB2DIR is the environment
variable exported by ~/sqllib/db2profile, and because DB2 allows you
to install into any directory on Windows I thought it made sense to
support alternate install directories using the same mechanism).

Now to actually put the code through its paces :)

Dan

On 3/8/05, ??? <yo...@li...> wrote:
> =20
> Oh, I've forgot to fix the notorious timestamp bug about the fraction par=
t=20
> :-(=20
>  =20
> I think I've fixed the bug right now and uploaded to the same place.=20
> You can get by anonymous ftp at
> people.linuxkorea.co.kr/pub/DB2/src.=20
> The filename is the same as the previous one.=20
>  =20
> Can you please check this for me?=20
>  =20
> Thanks.=20
>  =20
> FYI, I've include the ugly part related to timestamp string building:=20
>  =20
>         case SQL_C_TYPE_TIMESTAMP:
>                 timestampSt =3D *(TIMESTAMP_STRUCT *)(buf);
>                 size =3D 26 + 1;
>                 tempStr =3D (char *) MY_MALLOC(size);
>                 memset(tempStr, 0, size);
>                 sprintf(tempStr,
>                               =20
> "%04d-%02d-%02d-%02d.%02d.%02d.",
>                                 timestampSt.year,
>                                 timestampSt.month,
>                                 timestampSt.day,
>                                 timestampSt.hour,
>                                 timestampSt.minute,
>                                 timestampSt.second);=20
>  =20
>                 /* ffffff part */=20
>  =20
>                 fractionPart =3D (char *)MY_MALLOC(size);
>                 memset(fractionPart, 0, size);
>                 sprintf(fractionPart, "%09d", (unsigned
> int)timestampSt.fraction);
>                 fractionPart[6] =3D '\0';
>                 strcat(tempStr, fractionPart);=20
>  =20
>                 /* val =3D
> PyString_FromStringAndSize(tempStr, 26); */ /* paranoid? */
>                 val =3D PyString_FromString(tempStr);=20
>  =20
>                 MY_FREE(tempStr);
>                 MY_FREE(fractionPart);=20
>  =20
>                 break;
> =20
> =20
> ----- Original Message -----=20
> From: Jaco Smuts=20
> To: ???=20
> Cc: Dan Scott ; pyd...@li... ;
> pyd...@li...=20
> Sent: Wednesday, March 09, 2005 1:30 AM=20
> Subject: Re: [PyDB2-discuss] New release on sourceforge?=20
>=20
>=20
> I know little about C, but I'll gladly test it using some db2 scripts I u=
se
> at work=20
>=20
> does this codebase address the timestamp issue (there is a patch for it) =
?=20
>=20
>=20
>=20
>=20
> =20
>  "???" <yo...@li...>=20
> Sent by: pyd...@li...=20
>=20
> 2005/03/08 02:29 PM=20
> =20
> To "Dan Scott" <de...@gm...>,
> <pyd...@li...>=20
> =20
> cc=20
> =20
> Subject Re: [PyDB2-discuss] New release on sourceforge?
> =20
> =20
>=20
>=20
>=20
> Hi~ everyone,
>=20
> I've just refactored the module and uploaded to
> ftp://people.linuxkorea.co.kr/pub/DB2/src.
> Can you please review the source code?
>=20
> I'm sure that this version is much better than the previous one.
> It includes unittest code now.
>=20
> Sooner or later, I would like to upload this version to sf.net.
>=20
> ----- Original Message -----=20
> From: "Dan Scott" <de...@gm...>
> To: <pyd...@li...>
> Sent: Tuesday, February 01, 2005 6:20 AM
> Subject: Re: [PyDB2-discuss] New release on sourceforge?
>=20
>=20
> > On Mon, 31 Jan 2005 17:12:00 +0900, ??? <yo...@li...> wrote:
> >> Hi Dan,
> >>=20
> >> ----- 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?
> >>=20
> >>=20
> >> > Hi Yuval, Man-Yong:
> >> >
> >> > Any chance of that 1.0 release happening?
> >>=20
> >> Yuval, I want you to release 1.0.  In fact, I don't know how to releas=
e a
> new version in sf.net.
> >=20
> > Yuval, when you create the release, let me know and I'll update the
> > Python Package Index entry for the project.
> >=20
> >> > 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.
> >>=20
> >> Sure.
> >=20
> > Excellent!
> >=20
> >> > 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 sha=
dy
> >> > 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
> >>=20
> >> Of course!
> >=20
> > 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
> >=20
> > This is really exciting; with these steps in place I think this
> > project will really take off and become more active again.

Re: [PyDB2-discuss] New release on sourceforge?

[??? <yo...@li...>]

T2gsIEkndmUgZm9yZ290IHRvIGZpeCB0aGUgbm90b3Jpb3VzIHRpbWVzdGFtcCBidWcgYWJvdXQg
dGhlIGZyYWN0aW9uIHBhcnQgIDotKA0KDQpJIHRoaW5rIEkndmUgZml4ZWQgdGhlIGJ1ZyByaWdo
dCBub3cgYW5kIHVwbG9hZGVkIHRvIHRoZSBzYW1lIHBsYWNlLg0KWW91IGNhbiBnZXQgYnkgYW5v
bnltb3VzIGZ0cCBhdCBwZW9wbGUubGludXhrb3JlYS5jby5rci9wdWIvREIyL3NyYy4NClRoZSBm
aWxlbmFtZSBpcyB0aGUgc2FtZSBhcyB0aGUgcHJldmlvdXMgb25lLg0KDQpDYW4geW91IHBsZWFz
ZSBjaGVjayB0aGlzIGZvciBtZT8NCg0KVGhhbmtzLg0KDQpGWUksIEkndmUgaW5jbHVkZSB0aGUg
dWdseSBwYXJ0IHJlbGF0ZWQgdG8gdGltZXN0YW1wIHN0cmluZyBidWlsZGluZzoNCg0KICAgICAg
ICBjYXNlIFNRTF9DX1RZUEVfVElNRVNUQU1QOg0KICAgICAgICAgICAgICAgIHRpbWVzdGFtcFN0
ID0gKihUSU1FU1RBTVBfU1RSVUNUICopKGJ1Zik7DQogICAgICAgICAgICAgICAgc2l6ZSA9IDI2
ICsgMTsNCiAgICAgICAgICAgICAgICB0ZW1wU3RyID0gKGNoYXIgKikgTVlfTUFMTE9DKHNpemUp
Ow0KICAgICAgICAgICAgICAgIG1lbXNldCh0ZW1wU3RyLCAwLCBzaXplKTsNCiAgICAgICAgICAg
ICAgICBzcHJpbnRmKHRlbXBTdHIsDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICIl
MDRkLSUwMmQtJTAyZC0lMDJkLiUwMmQuJTAyZC4iLA0KICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICB0aW1lc3RhbXBTdC55ZWFyLA0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICB0aW1lc3RhbXBTdC5tb250aCwNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgdGlt
ZXN0YW1wU3QuZGF5LA0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB0aW1lc3RhbXBT
dC5ob3VyLA0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB0aW1lc3RhbXBTdC5taW51
dGUsDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHRpbWVzdGFtcFN0LnNlY29uZCk7
DQoNCiAgICAgICAgICAgICAgICAvKiBmZmZmZmYgcGFydCAqLw0KDQogICAgICAgICAgICAgICAg
ZnJhY3Rpb25QYXJ0ID0gKGNoYXIgKilNWV9NQUxMT0Moc2l6ZSk7DQogICAgICAgICAgICAgICAg
bWVtc2V0KGZyYWN0aW9uUGFydCwgMCwgc2l6ZSk7DQogICAgICAgICAgICAgICAgc3ByaW50Zihm
cmFjdGlvblBhcnQsICIlMDlkIiwgKHVuc2lnbmVkIGludCl0aW1lc3RhbXBTdC5mcmFjdGlvbik7
DQogICAgICAgICAgICAgICAgZnJhY3Rpb25QYXJ0WzZdID0gJ1wwJzsNCiAgICAgICAgICAgICAg
ICBzdHJjYXQodGVtcFN0ciwgZnJhY3Rpb25QYXJ0KTsNCg0KICAgICAgICAgICAgICAgIC8qIHZh
bCA9IFB5U3RyaW5nX0Zyb21TdHJpbmdBbmRTaXplKHRlbXBTdHIsIDI2KTsgKi8gLyogcGFyYW5v
aWQ/ICovDQogICAgICAgICAgICAgICAgdmFsID0gUHlTdHJpbmdfRnJvbVN0cmluZyh0ZW1wU3Ry
KTsNCg0KICAgICAgICAgICAgICAgIE1ZX0ZSRUUodGVtcFN0cik7DQogICAgICAgICAgICAgICAg
TVlfRlJFRShmcmFjdGlvblBhcnQpOw0KDQogICAgICAgICAgICAgICAgYnJlYWs7DQoNCiAgLS0t
LS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSANCiAgRnJvbTogSmFjbyBTbXV0cyANCiAgVG86ID8/
PyANCiAgQ2M6IERhbiBTY290dCA7IHB5ZGIyLWRpc2N1c3NAbGlzdHMuc291cmNlZm9yZ2UubmV0
IDsgcHlkYjItZGlzY3Vzcy1hZG1pbkBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQgDQogIFNlbnQ6IFdl
ZG5lc2RheSwgTWFyY2ggMDksIDIwMDUgMTozMCBBTQ0KICBTdWJqZWN0OiBSZTogW1B5REIyLWRp
c2N1c3NdIE5ldyByZWxlYXNlIG9uIHNvdXJjZWZvcmdlPw0KDQoNCg0KICBJIGtub3cgbGl0dGxl
IGFib3V0IEMsIGJ1dCBJJ2xsIGdsYWRseSB0ZXN0IGl0IHVzaW5nIHNvbWUgZGIyIHNjcmlwdHMg
SSB1c2UgYXQgd29yayANCg0KICBkb2VzIHRoaXMgY29kZWJhc2UgYWRkcmVzcyB0aGUgdGltZXN0
YW1wIGlzc3VlICh0aGVyZSBpcyBhIHBhdGNoIGZvciBpdCkgPyANCg0KDQoNCg0KICAgICAgICAi
Pz8/IiA8eW9uZ0BsaW51eGtvcmVhLmNvLmtyPiANCiAgICAgICAgU2VudCBieTogcHlkYjItZGlz
Y3Vzcy1hZG1pbkBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQgDQogICAgICAgIDIwMDUvMDMvMDggMDI6
MjkgUE0gDQogICAgICAgVG8gIkRhbiBTY290dCIgPGRlbmlhbHNAZ21haWwuY29tPiwgPHB5ZGIy
LWRpc2N1c3NAbGlzdHMuc291cmNlZm9yZ2UubmV0PiAgDQogICAgICAgICAgICAgIGNjICANCiAg
ICAgICAgICAgICAgU3ViamVjdCBSZTogW1B5REIyLWRpc2N1c3NdIE5ldyByZWxlYXNlIG9uIHNv
dXJjZWZvcmdlPyANCg0KICAgICAgICAgICAgICANCg0KICAgICAgIA0KDQoNCg0KICBIaX4gZXZl
cnlvbmUsDQoNCiAgSSd2ZSBqdXN0IHJlZmFjdG9yZWQgdGhlIG1vZHVsZSBhbmQgdXBsb2FkZWQg
dG8gZnRwOi8vcGVvcGxlLmxpbnV4a29yZWEuY28ua3IvcHViL0RCMi9zcmMuDQogIENhbiB5b3Ug
cGxlYXNlIHJldmlldyB0aGUgc291cmNlIGNvZGU/DQoNCiAgSSdtIHN1cmUgdGhhdCB0aGlzIHZl
cnNpb24gaXMgbXVjaCBiZXR0ZXIgdGhhbiB0aGUgcHJldmlvdXMgb25lLg0KICBJdCBpbmNsdWRl
cyB1bml0dGVzdCBjb2RlIG5vdy4NCg0KICBTb29uZXIgb3IgbGF0ZXIsIEkgd291bGQgbGlrZSB0
byB1cGxvYWQgdGhpcyB2ZXJzaW9uIHRvIHNmLm5ldC4NCg0KICAtLS0tLSBPcmlnaW5hbCBNZXNz
YWdlIC0tLS0tIA0KICBGcm9tOiAiRGFuIFNjb3R0IiA8ZGVuaWFsc0BnbWFpbC5jb20+DQogIFRv
OiA8cHlkYjItZGlzY3Vzc0BsaXN0cy5zb3VyY2Vmb3JnZS5uZXQ+DQogIFNlbnQ6IFR1ZXNkYXks
IEZlYnJ1YXJ5IDAxLCAyMDA1IDY6MjAgQU0NCiAgU3ViamVjdDogUmU6IFtQeURCMi1kaXNjdXNz
XSBOZXcgcmVsZWFzZSBvbiBzb3VyY2Vmb3JnZT8NCg0KDQogID4gT24gTW9uLCAzMSBKYW4gMjAw
NSAxNzoxMjowMCArMDkwMCwgPz8/IDx5b25nQGxpbnV4a29yZWEuY28ua3I+IHdyb3RlOg0KICA+
PiBIaSBEYW4sDQogID4+IA0KICA+PiAtLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tDQogID4+
IEZyb206ICJEYW4gU2NvdHQiIDxkZW5pYWxzQGdtYWlsLmNvbT4NCiAgPj4gVG86IDxweWRiMi1k
aXNjdXNzQGxpc3RzLnNvdXJjZWZvcmdlLm5ldD4NCiAgPj4gU2VudDogU3VuZGF5LCBKYW51YXJ5
IDMwLCAyMDA1IDU6MjQgQU0NCiAgPj4gU3ViamVjdDogUmU6IFtQeURCMi1kaXNjdXNzXSBOZXcg
cmVsZWFzZSBvbiBzb3VyY2Vmb3JnZT8NCiAgPj4gDQogID4+IA0KICA+PiA+IEhpIFl1dmFsLCBN
YW4tWW9uZzoNCiAgPj4gPg0KICA+PiA+IEFueSBjaGFuY2Ugb2YgdGhhdCAxLjAgcmVsZWFzZSBo
YXBwZW5pbmc/DQogID4+IA0KICA+PiBZdXZhbCwgSSB3YW50IHlvdSB0byByZWxlYXNlIDEuMC4g
IEluIGZhY3QsIEkgZG9uJ3Qga25vdyBob3cgdG8gcmVsZWFzZSBhIG5ldyB2ZXJzaW9uIGluIHNm
Lm5ldC4NCiAgPiANCiAgPiBZdXZhbCwgd2hlbiB5b3UgY3JlYXRlIHRoZSByZWxlYXNlLCBsZXQg
bWUga25vdyBhbmQgSSdsbCB1cGRhdGUgdGhlDQogID4gUHl0aG9uIFBhY2thZ2UgSW5kZXggZW50
cnkgZm9yIHRoZSBwcm9qZWN0Lg0KICA+IA0KICA+PiA+IEFsc28sIGl0IHdvdWxkIGJlIGEgcmVh
bGx5IG5pY2UgZm9sbG93LXVwIGlmIE1hbi1Zb25nIGNvdWxkIHByb2R1Y2UNCiAgPj4gPiB0aGUg
d2luMzIgYmluYXJpZXMgZm9yIHRoZSByZWxhdGl2ZWx5IHJlY2VudCBQeXRob24gMi40IHJlbGVh
c2UuDQogID4+IA0KICA+PiBTdXJlLg0KICA+IA0KICA+IEV4Y2VsbGVudCENCiAgPiANCiAgPj4g
PiBXaGVuIHlvdSBzdGFydCBkZXZlbG9waW5nIHRoZSAxLjEgYnJhbmNoLCB3b3VsZCB5b3UgY29u
c2lkZXINCiAgPj4gPiBpbnN0aXR1dGluZyBhIGJhc2ljIENvbnRyaWJ1dG9yIExpY2Vuc2UgQWdy
ZWVtZW50IChDTEEpIGxpa2UgRWNsaXBzZQ0KICA+PiA+IGFuZCBBcGFjaGUgZG8/IFRoZSBDTEEg
aXMgYSBsZWdhbCBwcm9jZXNzIHRoYXQgYXNrcyB3b3VsZC1iZQ0KICA+PiA+IGNvbnRyaWJ1dG9y
cyAmIHRoZSBjb250cmlidXRvcnMnIGVtcGxveWVycyB0byBzaWduIG9mZiBvbiBhIGZvcm0NCiAg
Pj4gPiBzdGF0aW5nIHRoYXQgdGhlIGNvZGUgdGhleSBhcmUgY29udHJpYnV0aW5nIGlzIHJpZ2h0
ZnVsbHkgdGhlaXJzIHRvDQogID4+ID4gY29udHJpYnV0ZSAtLSBiYXNpY2FsbHkgYSB3YXkgb2Yg
YXZvaWRpbmcgYW55IGNvbnRyaWJ1dGlvbnMgZnJvbSBzaGFkeQ0KICA+PiA+IHNvdXJjZXMuDQog
ID4+ID4NCiAgPj4gPiBNeSBlbXBsb3llciBpcyBhIGJpdCB3YXJ5IG9mIHByb2plY3RzIHRoYXQg
ZG9uJ3QgaGF2YSBhIENMQSBwcm9jZXNzLA0KICA+PiA+IHNvIEkgY2FuJ3QgYmUgdG9vIHVzZWZ1
bCB0byB0aGUgZWZmb3J0IHdpdGhvdXQgaXQgOiggVW5sZXNzIHlvdSBjYWxsDQogID4+ID4gc2Vu
ZGluZyByZXF1ZXN0cyBhbmQgbGl0dGxlIHJlbWluZGVyIG5vdGVzIHRvIHRoZSBtYWlsaW5nIGxp
c3QNCiAgPj4gPiB1c2VmdWwuLi4NCiAgPj4gPg0KICA+PiA+IERhbg0KICA+PiANCiAgPj4gT2Yg
Y291cnNlIQ0KICA+IA0KICA+IFRoYXQncyBncmVhdCEgRm9yIGZ1cnRoZXIgaW5mb3JtYXRpb24g
b24gdGhlIENvbnRyaWJ1dG9yIExpY2Vuc2luZw0KICA+IEFncmVlbWVudCAoUHl0aG9uIGl0c2Vs
ZiBhZG9wdGVkIGEgQ0xBIHByb2Nlc3MgZWFybGllciB0aGlzIG1vbnRoKSB5b3UNCiAgPiBjYW4g
bG9vayBhdCBodHRwOi8vd3d3LnB5dGhvbi5vcmcvcHNmL2NvbnRyaWIuaHRtbA0KICA+IA0KICA+
IFRoaXMgaXMgcmVhbGx5IGV4Y2l0aW5nOyB3aXRoIHRoZXNlIHN0ZXBzIGluIHBsYWNlIEkgdGhp
bmsgdGhpcw0KICA+IHByb2plY3Qgd2lsbCByZWFsbHkgdGFrZSBvZmYgYW5kIGJlY29tZSBtb3Jl
IGFjdGl2ZSBhZ2Fpbi4NCiAgPiANCiAgPiANCiAgPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQogID4gVGhpcyBTRi5OZXQgZW1haWwgaXMg
c3BvbnNvcmVkIGJ5OiBJbnRlbGxpVklFVyAtLSBJbnRlcmFjdGl2ZSBSZXBvcnRpbmcNCiAgPiBU
b29sIGZvciBvcGVuIHNvdXJjZSBkYXRhYmFzZXMuIENyZWF0ZSBkcmFnLSYtZHJvcCByZXBvcnRz
LiBTYXZlIHRpbWUNCiAgPiBieSBvdmVyIDc1JSEgUHVibGlzaCByZXBvcnRzIG9uIHRoZSB3ZWIu
IEV4cG9ydCB0byBET0MsIFhMUywgUlRGLCBldGMuDQogID4gRG93bmxvYWQgYSBGUkVFIGNvcHkg
YXQgaHR0cDovL3d3dy5pbnRlbGxpdmlldy5jb20vZ28vb3Nkbl9ubA0KICA+IF9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQogID4gUHlEQjItZGlzY3VzcyBt
YWlsaW5nIGxpc3QNCiAgPiBQeURCMi1kaXNjdXNzQGxpc3RzLnNvdXJjZWZvcmdlLm5ldA0KICA+
IGh0dHBzOi8vbGlzdHMuc291cmNlZm9yZ2UubmV0L2xpc3RzL2xpc3RpbmZvL3B5ZGIyLWRpc2N1
c3MNCiAgPiANCg==

Re: [PyDB2-discuss] New release on sourceforge?

[??? <yo...@li...>]

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==

[PyDB2-discuss] Use of parameters in pydb2

[Torre de l. J. <j....@BG...>]

Hi all,

Trying to make pydb2 in my project I had to make a little change in the =
code.
I need to use parameters in the SQL statements but they seem not work =
very fine. The type detection of the parameters does not work properly =
with Unicode strings.
That's why I changed in line 464 of DB2.py where it says:

        elif type(q) =3D=3D type(''):

for

        elif type(q) =3D=3D type(unicode(' ')):

If not the Unicode strings are not detected as strings and not embrace =
with '' in the SQL statements.

Is that Ok?

Cheers.

Javier de la Torre
Botanic Garden and Botanical Museum Berlin Dahlem. FUB
Department of  Biodiversity Informatics and Laboratories
K=F6nigin-Luise-Str 6-8, D - 14191 Berlin
email     j....@bg...
phone +49(30) 838-50284=20
URL http://www.bgbm.org/torre
=20

[PyDB2-discuss] SQLSTATE 01517 - A character that could not be converted was replaced with a substitute character

[Torre de l. J. <j....@BG...>]

Hi all,

This is my first message to the mailing list. I've tried to find an
answer to my problems in the archive but I did not succeed.

So, here it goes: I am getting an error "SQLSTATE 01517 - A character
that could not be converted was replaced with a substitute character"
when doing a search trough pydb2. The same SQL works fine trough the
Control center.
I've read in a web page that I have to set the appropiate value for
db2codepage in the client.

I am not sure what this mean, but I suposse it has do something with
setting up my database as UTF-8.

I am using a Windows XP environment with DB2 v8.1.7.445 (SQL08020)
Personal Developer Edition.

Does anyone have this problem?

Thanks in avance.

Javier de la Torre.

Re: [PyDB2-discuss] New release on sourceforge?

[Dan S. <de...@gm...>]

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.

Re: [PyDB2-discuss] New release on sourceforge?

[??? <yo...@li...>]

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=

Re: [PyDB2-discuss] New release on sourceforge?

[Dan S. <de...@gm...>]

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.
> 
>

[PyDB2-discuss] Re: I have a patch to handle SQL_SUCCESS_WITH_INFO

[Preston L. <pla...@jo...>]

It sounds like there may be a new release of the PyDB2 module coming up 
soon...

Is there any interest in accepting this patch to handle the
SQL_SUCCESS_WITH_INFO state?  Not handling this is kind of a release
critical bug for PyDB2 as used in my company, since a valid query in my
app produces this result.

I should have access to check it in through my Sourceforge account
(planders) I just haven't gotten to it yet.  There was also some concern
about the handling of the "info".  I was stashing it in the
LastWarningString variable.  Primitive, I know, but I don't have any
better ideas at this point.

thanks,

Preston Landers  (512) 225-3929 |         
     pla...@jo...       | "For 'tis the sport to have the enginer
   Senior Software Developer    |  Hoist with his owne petar" 
  Journyx, Austin, Texas, USA   |     -- Shakespeare, Hamlet III iv.


---------- Forwarded message ----------
Date: Thu, 15 Jan 2004 11:12:33 -0600 (CST)
From: Preston Landers <pla...@jo...>
To: pyd...@li...
Subject: [PyDB2-discuss] Re: I have a patch to handle SQL_SUCCESS_WITH_INFO

On Wed, 14 Jan 2004, Preston Landers wrote:

> We ran into a situation recently where we wanted to use a certain
> construct in DB2 that was generating the SQL0347W warning about recursion.
> The DB2.py driver was raising this non-fatal warning as a error (and not
> returning the result rows.)
>
> Digging a bit deeper I found that this is the SQL_SUCCESS_WITH_INFO result
> code.  The current driver (_db2_module.c) has a comment to the effect of
> "need to cope with SQL_SUCCESS_WITH_INFO."
>
> I took what seemed to me to be the most simple and direct route to fix
> this problem.  I simply added a 'LastWarningString' attribute to the
> internal cursor object.  This is cleared before every statement execution.
> If SQL_SUCCESS_WITH_INFO is encountered then LastWarningString is updated
> with the warning text, and the result rows are returned.
>
> It is then up to the caller to check LastWarningString after every query
> if they care about that.  I also made a minor change in DB2.py BaseCursor
> class to copy over the LastWarningString in _refresh_info().


Attached are the three files that I modified to make this change.

_db2_module.c  -- handle SQL_SUCCESS_WITH_INFO by setting the warning
                  to a cursor variable LastWarningString

DB2.py  -- copy over LastWarningString in _refresh_info().
           Also changed 'x in dict' Python 2.2 syntax to the
           equivelent has_key() so it will work with Py 2.1.

README -- just added a note about checking LastWarningString

By the way, my Sourceforge account is 'planders'.

thanks,

---
Preston Landers - pla...@jo...
Senior Software Developer, Journyx, Inc.
Austin, Texas  (512) 225-3929

Re: [PyDB2-discuss] New release on sourceforge?

[Yuval T. <yu...@ad...>]

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.

Re: [PyDB2-discuss] New release on sourceforge?

[Yuval T. <yu...@ad...>]

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.

Re: [PyDB2-discuss] New release on sourceforge?

[??? <yo...@li...>]

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=

Re: [PyDB2-discuss] New release on sourceforge?

[Yuval T. <yu...@ad...>]

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.

Re: [PyDB2-discuss] New release on sourceforge?

[Patrick K. O'B. <po...@or...>]

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

[PyDB2-discuss] New release on sourceforge?

[Dan S. <de...@gm...>]

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

Re: [PyDB2-discuss] Calling stored procedures

[Dan S. <de...@gm...>]

Hi Man-Yong:

Well, pyDB2 has filled a heck of a gap in the meantime, and I thank you for it.

In theory, nextset() should be relatively easy to implement at least;
in CLI/ODBC you could call SQLMoreResults() (
http://publib.boulder.ibm.com/infocenter/db2help/topic/com.ibm.db2.udb.doc/ad/r0000628.htm)
and either set the Python Cursor object to None if the result is
SQL_NO_DATA_FOUND or prepare the Cursor object to fetch the next
result set if the result is SQL_SUCCESS.

Dan


On Mon, 6 Dec 2004 14:35:38 +0900, ??? <yo...@li...> wrote:
> Hi~
> 
> Currently, stored procedure support in PyDB2 is incomplete and not tested thoroughly.
> As you can see, nextset() method is missing now.
> 
> PyDB2 needs severe reworking right now, 'cause it was started just for my project's need
> and most of all, I'm not a DB2 specialist.  Personally, I haven't used any stored procedure in my real projects :(
> 
> You know we can get lots of hints from other Python database modules like MySQLdb and DCOracle*.
> After reviewing them, I can start coding afresh, I think.
> 
> Thanks,
> Man-Yong
> 
> 
> 
> ----- Original Message -----
> From: "Dan Scott" <de...@gm...>
> To: <pyd...@li...>
> Sent: Sunday, December 05, 2004 1:58 PM
> Subject: [PyDB2-discuss] Calling stored procedures
> 
> > Hi:
> >
> > I noticed there is no documentation in the README about stored
> > procedure support, so I went ahead to try it out according to the
> > interface defined by PEP249.
> >
> > Env: DB2 V8.2, Windows XP, Python 2.3, pyDB2 0.998a installed from
> > Man-Yong Lee's binary.
> >
> > I started by creating a simple SQL stored procedure to test the INOUT
> > parameter support:
> >
> >    CREATE PROCEDURE test_date(INOUT date DATE)
> >    BEGIN
> >      SET date = '2007-01-05';
> >    END
> >
> > ... then called it from the following method:
> >
> > def call_procedure_inout(conn):
> >    """
> >    Call a procedure that accepts one INOUT DATE parameter.
> >    """
> >
> >    curs=conn.cursor()
> >    stmt = 'TEST_DATE'
> >    parm = ('2004-12-02')
> > #    parm = ('10/27/1991')
> >    res = curs.callproc(stmt, parm)
> >    return res
> >
> > The expected return value would be '2007-01-05', but I get an error instead:
> >
> > *****
> >  File "C:\local\python2.3\Lib\site-packages\DB2.py", line 438, in callproc
> >    r = self._cs.callproc(procname.upper(), t_args)
> > _db2.error:
> >
> > SQLSTATE : 22007, NATIVE ERROR CODE : -99999
> >
> > [IBM][CLI Driver] CLI0113E  SQLSTATE 22007: An invalid datetime format
> > was detected; that is, an invalid string representation or value was
> > specified. SQLSTATE=22007
> > *****
> >
> > As you can see, I've tried a couple of alternative date-time formats.
> > No luck. I then changed the CREATE PROCEDURE statement to specify a
> > VARCHAR(16) INOUT parameter to simplify the testcase by avoiding any
> > datetime weirdness, but ended up getting the same value I had passed
> > into the stored procedure, instead of having it set by the stored
> > procedure to some other value. Finally, I changed the stored procedure
> > signature to a single OUT parameter, but still didn't find that
> > .callproc ended up returning any changed input sequence values. When I
> > call these stored proecedures from the command line, they perform as I
> > expected.
> >
> > So, does pyDB2 support INOUT or OUT parameters?
> >
> > Also, I created the rsultset.db2 sample stored procedure shipped in
> > the SQLLIB/samples/sqlproc directory, then tried calling it from
> > Python. I was able to retrieve the first result set from the stored
> > procedure, but when I called curs.nextset() I received an error:
> >  AttributeError: Cursor instance has no attribute 'nextset'
> >
> > So it looks like pyDB2 doesn't support stored procedures that return
> > multiple result sets through the Cursor.nextset() method -- is this
> > correct?
> >
> > Thanks,
> > Dan
> >
> > 
> > -------------------------------------------------------
> > SF email is sponsored by - The IT Product Guide
> > Read honest & candid reviews on hundreds of IT Products from real users.
> > Discover which products truly live up to the hype. Start reading now.
> > http://productguide.itmanagersjournal.com/
> > _______________________________________________
> > PyDB2-discuss mailing list
> > PyD...@li...
> > https://lists.sourceforge.net/lists/listinfo/pydb2-discuss
> >

Re: [PyDB2-discuss] Calling stored procedures

[Yuval T. <yu...@ad...>]

On Monday 06 December 2004 07:35, ??? wrote:
> You know we can get lots of hints from other Python database modules like
> MySQLdb and DCOracle*. After reviewing them, I can start coding afresh, I
> think.

I've been meaning to say this for a long time now... :-)
Well, I actually started to implement a MySQLdb-like module - which basically 
means, implement only the basics in C and the rest in python (I think it 
comes out to be implementing the connection object in C and the cursors in 
python - similar to MySQLdb).  I stopped working on it a while ago - I've 
been meaning to post the idea before I get serious with it.
I'm pretty familiar with DB2 (not a lot, but enough) and with the current DB2 
module.  So maybe now's a good time to get back on it - I'm in.  Anybody 
else ? :-)

-- 
Yuval Turgeman
Content Technology, Aduva LTD.

Re: [PyDB2-discuss] Calling stored procedures

[??? <yo...@li...>]

SGl+DQoNCkN1cnJlbnRseSwgc3RvcmVkIHByb2NlZHVyZSBzdXBwb3J0IGluIFB5REIyIGlzIGlu
Y29tcGxldGUgYW5kIG5vdCB0ZXN0ZWQgdGhvcm91Z2hseS4NCkFzIHlvdSBjYW4gc2VlLCBuZXh0
c2V0KCkgbWV0aG9kIGlzIG1pc3Npbmcgbm93Lg0KDQpQeURCMiBuZWVkcyBzZXZlcmUgcmV3b3Jr
aW5nIHJpZ2h0IG5vdywgJ2NhdXNlIGl0IHdhcyBzdGFydGVkIGp1c3QgZm9yIG15IHByb2plY3Qn
cyBuZWVkDQphbmQgbW9zdCBvZiBhbGwsIEknbSBub3QgYSBEQjIgc3BlY2lhbGlzdC4gIFBlcnNv
bmFsbHksIEkgaGF2ZW4ndCB1c2VkIGFueSBzdG9yZWQgcHJvY2VkdXJlIGluIG15IHJlYWwgcHJv
amVjdHMgOigNCg0KWW91IGtub3cgd2UgY2FuIGdldCBsb3RzIG9mIGhpbnRzIGZyb20gb3RoZXIg
UHl0aG9uIGRhdGFiYXNlIG1vZHVsZXMgbGlrZSBNeVNRTGRiIGFuZCBEQ09yYWNsZSouDQpBZnRl
ciByZXZpZXdpbmcgdGhlbSwgSSBjYW4gc3RhcnQgY29kaW5nIGFmcmVzaCwgSSB0aGluay4NCg0K
VGhhbmtzLA0KTWFuLVlvbmcNCg0KLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSANCkZyb206
ICJEYW4gU2NvdHQiIDxkZW5pYWxzQGdtYWlsLmNvbT4NClRvOiA8cHlkYjItZGlzY3Vzc0BsaXN0
cy5zb3VyY2Vmb3JnZS5uZXQ+DQpTZW50OiBTdW5kYXksIERlY2VtYmVyIDA1LCAyMDA0IDE6NTgg
UE0NClN1YmplY3Q6IFtQeURCMi1kaXNjdXNzXSBDYWxsaW5nIHN0b3JlZCBwcm9jZWR1cmVzDQoN
Cg0KPiBIaToNCj4gDQo+IEkgbm90aWNlZCB0aGVyZSBpcyBubyBkb2N1bWVudGF0aW9uIGluIHRo
ZSBSRUFETUUgYWJvdXQgc3RvcmVkDQo+IHByb2NlZHVyZSBzdXBwb3J0LCBzbyBJIHdlbnQgYWhl
YWQgdG8gdHJ5IGl0IG91dCBhY2NvcmRpbmcgdG8gdGhlDQo+IGludGVyZmFjZSBkZWZpbmVkIGJ5
IFBFUDI0OS4NCj4gDQo+IEVudjogREIyIFY4LjIsIFdpbmRvd3MgWFAsIFB5dGhvbiAyLjMsIHB5
REIyIDAuOTk4YSBpbnN0YWxsZWQgZnJvbQ0KPiBNYW4tWW9uZyBMZWUncyBiaW5hcnkuDQo+IA0K
PiBJIHN0YXJ0ZWQgYnkgY3JlYXRpbmcgYSBzaW1wbGUgU1FMIHN0b3JlZCBwcm9jZWR1cmUgdG8g
dGVzdCB0aGUgSU5PVVQNCj4gcGFyYW1ldGVyIHN1cHBvcnQ6DQo+IA0KPiAgICBDUkVBVEUgUFJP
Q0VEVVJFIHRlc3RfZGF0ZShJTk9VVCBkYXRlIERBVEUpDQo+ICAgIEJFR0lODQo+ICAgICAgU0VU
IGRhdGUgPSAnMjAwNy0wMS0wNSc7DQo+ICAgIEVORA0KPiANCj4gLi4uIHRoZW4gY2FsbGVkIGl0
IGZyb20gdGhlIGZvbGxvd2luZyBtZXRob2Q6DQo+IA0KPiBkZWYgY2FsbF9wcm9jZWR1cmVfaW5v
dXQoY29ubik6DQo+ICAgICIiIg0KPiAgICBDYWxsIGEgcHJvY2VkdXJlIHRoYXQgYWNjZXB0cyBv
bmUgSU5PVVQgREFURSBwYXJhbWV0ZXIuDQo+ICAgICIiIg0KPiAgICANCj4gICAgY3Vycz1jb25u
LmN1cnNvcigpDQo+ICAgIHN0bXQgPSAnVEVTVF9EQVRFJw0KPiAgICBwYXJtID0gKCcyMDA0LTEy
LTAyJykNCj4gIyAgICBwYXJtID0gKCcxMC8yNy8xOTkxJykNCj4gICAgcmVzID0gY3Vycy5jYWxs
cHJvYyhzdG10LCBwYXJtKQ0KPiAgICByZXR1cm4gcmVzDQo+IA0KPiBUaGUgZXhwZWN0ZWQgcmV0
dXJuIHZhbHVlIHdvdWxkIGJlICcyMDA3LTAxLTA1JywgYnV0IEkgZ2V0IGFuIGVycm9yIGluc3Rl
YWQ6DQo+IA0KPiAqKioqKg0KPiAgRmlsZSAiQzpcbG9jYWxccHl0aG9uMi4zXExpYlxzaXRlLXBh
Y2thZ2VzXERCMi5weSIsIGxpbmUgNDM4LCBpbiBjYWxscHJvYw0KPiAgICByID0gc2VsZi5fY3Mu
Y2FsbHByb2MocHJvY25hbWUudXBwZXIoKSwgdF9hcmdzKQ0KPiBfZGIyLmVycm9yOiANCj4gDQo+
IFNRTFNUQVRFIDogMjIwMDcsIE5BVElWRSBFUlJPUiBDT0RFIDogLTk5OTk5DQo+IA0KPiBbSUJN
XVtDTEkgRHJpdmVyXSBDTEkwMTEzRSAgU1FMU1RBVEUgMjIwMDc6IEFuIGludmFsaWQgZGF0ZXRp
bWUgZm9ybWF0DQo+IHdhcyBkZXRlY3RlZDsgdGhhdCBpcywgYW4gaW52YWxpZCBzdHJpbmcgcmVw
cmVzZW50YXRpb24gb3IgdmFsdWUgd2FzDQo+IHNwZWNpZmllZC4gU1FMU1RBVEU9MjIwMDcNCj4g
KioqKioNCj4gDQo+IEFzIHlvdSBjYW4gc2VlLCBJJ3ZlIHRyaWVkIGEgY291cGxlIG9mIGFsdGVy
bmF0aXZlIGRhdGUtdGltZSBmb3JtYXRzLiANCj4gTm8gbHVjay4gSSB0aGVuIGNoYW5nZWQgdGhl
IENSRUFURSBQUk9DRURVUkUgc3RhdGVtZW50IHRvIHNwZWNpZnkgYQ0KPiBWQVJDSEFSKDE2KSBJ
Tk9VVCBwYXJhbWV0ZXIgdG8gc2ltcGxpZnkgdGhlIHRlc3RjYXNlIGJ5IGF2b2lkaW5nIGFueQ0K
PiBkYXRldGltZSB3ZWlyZG5lc3MsIGJ1dCBlbmRlZCB1cCBnZXR0aW5nIHRoZSBzYW1lIHZhbHVl
IEkgaGFkIHBhc3NlZA0KPiBpbnRvIHRoZSBzdG9yZWQgcHJvY2VkdXJlLCBpbnN0ZWFkIG9mIGhh
dmluZyBpdCBzZXQgYnkgdGhlIHN0b3JlZA0KPiBwcm9jZWR1cmUgdG8gc29tZSBvdGhlciB2YWx1
ZS4gRmluYWxseSwgSSBjaGFuZ2VkIHRoZSBzdG9yZWQgcHJvY2VkdXJlDQo+IHNpZ25hdHVyZSB0
byBhIHNpbmdsZSBPVVQgcGFyYW1ldGVyLCBidXQgc3RpbGwgZGlkbid0IGZpbmQgdGhhdA0KPiAu
Y2FsbHByb2MgZW5kZWQgdXAgcmV0dXJuaW5nIGFueSBjaGFuZ2VkIGlucHV0IHNlcXVlbmNlIHZh
bHVlcy4gV2hlbiBJDQo+IGNhbGwgdGhlc2Ugc3RvcmVkIHByb2VjZWR1cmVzIGZyb20gdGhlIGNv
bW1hbmQgbGluZSwgdGhleSBwZXJmb3JtIGFzIEkNCj4gZXhwZWN0ZWQuDQo+IA0KPiBTbywgZG9l
cyBweURCMiBzdXBwb3J0IElOT1VUIG9yIE9VVCBwYXJhbWV0ZXJzPw0KPiANCj4gQWxzbywgSSBj
cmVhdGVkIHRoZSByc3VsdHNldC5kYjIgc2FtcGxlIHN0b3JlZCBwcm9jZWR1cmUgc2hpcHBlZCBp
bg0KPiB0aGUgU1FMTElCL3NhbXBsZXMvc3FscHJvYyBkaXJlY3RvcnksIHRoZW4gdHJpZWQgY2Fs
bGluZyBpdCBmcm9tDQo+IFB5dGhvbi4gSSB3YXMgYWJsZSB0byByZXRyaWV2ZSB0aGUgZmlyc3Qg
cmVzdWx0IHNldCBmcm9tIHRoZSBzdG9yZWQNCj4gcHJvY2VkdXJlLCBidXQgd2hlbiBJIGNhbGxl
ZCBjdXJzLm5leHRzZXQoKSBJIHJlY2VpdmVkIGFuIGVycm9yOg0KPiAgQXR0cmlidXRlRXJyb3I6
IEN1cnNvciBpbnN0YW5jZSBoYXMgbm8gYXR0cmlidXRlICduZXh0c2V0Jw0KPiANCj4gU28gaXQg
bG9va3MgbGlrZSBweURCMiBkb2Vzbid0IHN1cHBvcnQgc3RvcmVkIHByb2NlZHVyZXMgdGhhdCBy
ZXR1cm4NCj4gbXVsdGlwbGUgcmVzdWx0IHNldHMgdGhyb3VnaCB0aGUgQ3Vyc29yLm5leHRzZXQo
KSBtZXRob2QgLS0gaXMgdGhpcw0KPiBjb3JyZWN0Pw0KPiANCj4gVGhhbmtzLA0KPiBEYW4NCj4g
DQo+IA0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tDQo+IFNGIGVtYWlsIGlzIHNwb25zb3JlZCBieSAtIFRoZSBJVCBQcm9kdWN0IEd1aWRl
DQo+IFJlYWQgaG9uZXN0ICYgY2FuZGlkIHJldmlld3Mgb24gaHVuZHJlZHMgb2YgSVQgUHJvZHVj
dHMgZnJvbSByZWFsIHVzZXJzLg0KPiBEaXNjb3ZlciB3aGljaCBwcm9kdWN0cyB0cnVseSBsaXZl
IHVwIHRvIHRoZSBoeXBlLiBTdGFydCByZWFkaW5nIG5vdy4gDQo+IGh0dHA6Ly9wcm9kdWN0Z3Vp
ZGUuaXRtYW5hZ2Vyc2pvdXJuYWwuY29tLw0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXw0KPiBQeURCMi1kaXNjdXNzIG1haWxpbmcgbGlzdA0KPiBQeURC
Mi1kaXNjdXNzQGxpc3RzLnNvdXJjZWZvcmdlLm5ldA0KPiBodHRwczovL2xpc3RzLnNvdXJjZWZv
cmdlLm5ldC9saXN0cy9saXN0aW5mby9weWRiMi1kaXNjdXNzDQo+

[PyDB2-discuss] Calling stored procedures

[Dan S. <de...@gm...>]

Hi:

I noticed there is no documentation in the README about stored
procedure support, so I went ahead to try it out according to the
interface defined by PEP249.

Env: DB2 V8.2, Windows XP, Python 2.3, pyDB2 0.998a installed from
Man-Yong Lee's binary.

I started by creating a simple SQL stored procedure to test the INOUT
parameter support:

    CREATE PROCEDURE test_date(INOUT date DATE)
    BEGIN
      SET date = '2007-01-05';
    END

... then called it from the following method:

def call_procedure_inout(conn):
    """
    Call a procedure that accepts one INOUT DATE parameter.
    """
    
    curs=conn.cursor()
    stmt = 'TEST_DATE'
    parm = ('2004-12-02')
#    parm = ('10/27/1991')
    res = curs.callproc(stmt, parm)
    return res

The expected return value would be '2007-01-05', but I get an error instead:

*****
  File "C:\local\python2.3\Lib\site-packages\DB2.py", line 438, in callproc
    r = self._cs.callproc(procname.upper(), t_args)
_db2.error: 

SQLSTATE : 22007, NATIVE ERROR CODE : -99999

[IBM][CLI Driver] CLI0113E  SQLSTATE 22007: An invalid datetime format
was detected; that is, an invalid string representation or value was
specified. SQLSTATE=22007
*****

As you can see, I've tried a couple of alternative date-time formats. 
No luck. I then changed the CREATE PROCEDURE statement to specify a
VARCHAR(16) INOUT parameter to simplify the testcase by avoiding any
datetime weirdness, but ended up getting the same value I had passed
into the stored procedure, instead of having it set by the stored
procedure to some other value. Finally, I changed the stored procedure
signature to a single OUT parameter, but still didn't find that
.callproc ended up returning any changed input sequence values. When I
call these stored proecedures from the command line, they perform as I
expected.

So, does pyDB2 support INOUT or OUT parameters?

Also, I created the rsultset.db2 sample stored procedure shipped in
the SQLLIB/samples/sqlproc directory, then tried calling it from
Python. I was able to retrieve the first result set from the stored
procedure, but when I called curs.nextset() I received an error:
  AttributeError: Cursor instance has no attribute 'nextset'

So it looks like pyDB2 doesn't support stored procedures that return
multiple result sets through the Cursor.nextset() method -- is this
correct?

Thanks,
Dan

Re: [PyDB2-discuss] Python Package Index entry for pyDB2

[<po...@or...>]

Dan Scott <de...@gm...> writes:

> Hello:
> 
> I took the liberty of adding pyDB2 to the Python Package Index  (PyPi)
> (http://www.python.org/pypi?:action=display&name=pyDB2&version=0.996a)
> to help other people find out about this great module.

Thank you very much, Dan.  Much appreciated.

-- 
Patrick K. O'Brien
Orbtech    http://www.orbtech.com
Pypersyst  http://www.pypersyst.org
Schevo     http://www.schevo.org

[PyDB2-discuss] Python Package Index entry for pyDB2

[Dan S. <de...@gm...>]

Hello:

I took the liberty of adding pyDB2 to the Python Package Index  (PyPi)
(http://www.python.org/pypi?:action=display&name=pyDB2&version=0.996a)
to help other people find out about this great module.

I inserted Man-Yong Lee's name as the author of the module,  and put
Patrick's name as the maintainer (since the Sourceforge project is
under his name). If either of you want to be able to edit the PyPi 
record for pyDB2, just tell me what your Python.org username is and
I'll happily assign admin privileges to you.

From what I understand, the new  "python setup.py register" command
should automatically update this information in PyPi if you've set
things up appropriately
(http://www.python.org/~jeremy/weblog/030924.html).

Dan