From lane@cycletime.com Wed Sep 6 16:18:45 2000 From: lane@cycletime.com (Lane Stevens) Date: Wed, 6 Sep 2000 09:18:45 -0600 Subject: [DB-SIG] Follow up to DCOracle-1.3.0 try/except of 4 August Message-ID: <20000906091845.E819@jisca.cycletime.com> If an error during connection occurs, the exception that is raised is OracleError rather than DCOracle.error. It appears that this exception originates in the c portion of the oci API. Is OracleError defined anywhere that can be imported so that error can be caught? It is my assumption that prior to creation of a valid db connection, OracleError is raised. Once a valid connection to the db has been made, DCOracle.error is raised. Is this assumption correct? Are there other exceptions that are raised by the DCOracle components? Thanks, Lane. -- Lane Stevens Terrapin Technologies, Inc. http://www.cycletime.com From prodgers@stsi.net Fri Sep 8 14:05:36 2000 From: prodgers@stsi.net (Philip Rodgers) Date: Fri, 08 Sep 2000 09:05:36 -0400 Subject: [DB-SIG] solaris compile of DCOracle Message-ID: <39B8E420.484759E5@stsi.net> i get the following error when try to make -f Makefile.pre.in boot PYTHON=python of solaris 2.7 can anyone lead me in the right direction? ... /usr/local/lib/python1.5/config/Makefile >sedscript echo "/^#@SET_CCC@/d" >>sedscript echo "/^installdir=/s%=.*%= /usr/local%" >>sedscript echo "/^exec_installdir=/s%=.*%=/usr/local%" >>sedscript echo "/^srcdir=/s%=.*%= .%" >>sedscript echo "/^VPATH=/s%=.*%= .%" >>sedscript echo "/^LINKPATH=/s%=.*%= %" >>sedscript echo "/^BASELIB=/s%=.*%= %" >>sedscript echo "/^BASESETUP=/s%=.*%= %" >>sedscript sed -f sedscript ./Makefile.pre.in >Makefile.pre /usr/local/lib/python1.5/config/makesetup \ -m Makefile.pre -c /usr/local/lib/python1.5/config/config.c.in Setup -n /usr/local/lib/python1.5/config/Setup bad word Buffer.c*noobjects* in Buffer Buffer.c*noobjects* make[1]: *** [Makefile] Error 1 make[1]: Leaving directory `/export/home/u0/prodgers/DCOracle/src' make: *** [boot] Error 2 -- ********************************************************************* * Philip Rodgers SouthNet Telecomm Services, Inc * * prodgers@stsi.net Developer * * * * "Of course I'm not busy, I did it right the first time." * ********************************************************************* From Cary Collett Tue Sep 12 22:08:47 2000 From: Cary Collett (Cary Collett) Date: Tue, 12 Sep 2000 17:08:47 -0400 Subject: [DB-SIG] MySQLdb for Python on windows? In-Reply-To: <20000620004803.B11388@arioch>; from eric@mixadlive.com on Tue, Jun 20, 2000 at 12:48:03AM +0000 References: <20000526105316.A470@arioch> <20000620004803.B11388@arioch> Message-ID: <20000912170847.K8129@ratatosk.org> As the subject says... is there a mysql module for Python on windows? Cary From rprice@unival.com Fri Sep 15 17:02:43 2000 From: rprice@unival.com (ray) Date: Fri, 15 Sep 2000 09:02:43 -0700 Subject: [DB-SIG] DB2 connectivity Message-ID: <39C24823.E9C916E9@unival.com> Hi, We recently purchased DB2 and need connectivity from Python. Has anybody successfully connected to DB2 (preferably v7.1) on ANY platform (preferably Linux)? If so, how? Any advice is appreciated. Ray From pobrien@orbtech.com Sun Sep 17 15:03:38 2000 From: pobrien@orbtech.com (Patrick K. O'Brien) Date: Sun, 17 Sep 2000 09:03:38 -0500 Subject: [DB-SIG] MySQLdb for Python on windows? In-Reply-To: <20000912170847.K8129@ratatosk.org> Message-ID: Apparently so, according to this recent python.faqts entry: http://www.faqts.com/knowledge-base/view.phtml/aid/4188/fid/395/lang/en --- Patrick K. O'Brien Orbtech (http://www.orbtech.com) "I am, therefore I think." -----Original Message----- From: db-sig-admin@python.org [mailto:db-sig-admin@python.org]On Behalf Of Cary Collett Sent: Tuesday, September 12, 2000 4:09 PM To: db-sig@python.org Subject: [DB-SIG] MySQLdb for Python on windows? As the subject says... is there a mysql module for Python on windows? Cary _______________________________________________ DB-SIG maillist - DB-SIG@python.org http://www.python.org/mailman/listinfo/db-sig From kadabra@visto.com Thu Sep 21 23:12:08 2000 From: kadabra@visto.com (oto pumerantz) Date: Thu, 21 Sep 2000 15:12:08 -0700 Subject: [DB-SIG] new mysql - module incompatibility Message-ID: <20000921221209.6DBF31CDDA@dinsdale.python.org> i am using=20 MySQL-python-1.4-2.i386.rpm it works well, but not with MySQL-client-3.23.22-1 (libmysqlclient.so.9 vs. libmysqlclient.so.6) is there a simple workaround? thanks. --------------------------------! _________________________________________________________________________= __ Visit http://www.visto.com/info, your free web-based communications cente= r. Visto.com. Life on the Dot. From adustman@globix.net Fri Sep 29 21:34:32 2000 From: adustman@globix.net (Andy Dustman) Date: Fri, 29 Sep 2000 16:34:32 -0400 (EDT) Subject: [DB-SIG] new mysql - module incompatibility In-Reply-To: <20000921221209.6DBF31CDDA@dinsdale.python.org> Message-ID: On Thu, 21 Sep 2000, oto pumerantz wrote: > i am using > MySQL-python-1.4-2.i386.rpm > > it works well, but not with MySQL-client-3.23.22-1 > (libmysqlclient.so.9 vs. libmysqlclient.so.6) > > is there a simple workaround? Don't use MySQL-python-1.4-2.i386.rpm? MySQLmodule-1.4 doesn't work with MySQL 3.22, let along 3.23. Try: http://dustman.net/andy/python/MySQLdb/0.2.2/MySQL-python-0.2.2-3.i386.rpm There is a file in there that MAY help you: /usr/doc/MySQL-python-0.2.2/CompatMysqldb.py This is MySQLmodule's Mysqldb module adapted to use _mysql (low-level part of MySQLdb). It's somewhat experimental. -- andy dustman | programmer | comstar.net is part of the Globix network telephone: 770.485.6025 / 706.549.7689 | icq: 32922760 | pgp: 0xc72f3f1d "Therefore, sweet knights, if you may doubt your strength or courage, come no further, for death awaits you all, with nasty, big, pointy teeth!"