From andy@dustman.net Fri Dec 1 02:50:22 2000 From: andy@dustman.net (Andy Dustman) Date: Thu, 30 Nov 2000 21:50:22 -0500 (EST) Subject: [DB-SIG] MySQLdb-0.3.0 is released Message-ID: Get it at: http://dustman.net/andy/python/MySQLdb/0.3.0 Major notes of interest: Should work with current versions of MySQL-3.22 and 3.23, and Python versions 1.5.2, 1.6 (not tested), and 2.0 (very lightly tested). Got to have Distutils (not included with Python 1.5.2, get it from www.python.org) to build. If you have to tweak setup.py (the build script) for your platform, send me your tweaks, and I will try to accomodate them. NO, I do not have a pre-compiled Windows version. I don't do (MS) Windows. The setup.py script *should* be able to make one. Read the docs for Distutils. If you succeed in making one, let me know about it. You should also be able to build RPMs. I am not distributing any yet because there are just too many possibilities. *** GPL *** Yes, the GPL is now a license option. I'm hedging simply because of all the controversy regarding recent Python licenses. -- Andy Dustman PGP: 0xC72F3F1D @ .net http://dustman.net/andy From uche.ogbuji@fourthought.com Fri Dec 1 11:16:05 2000 From: uche.ogbuji@fourthought.com (uche.ogbuji@fourthought.com) Date: Fri, 1 Dec 2000 04:16:05 -0700 Subject: [DB-SIG] ANN: 4Suite 0.10.0 Message-ID: <200012011116.EAA09806@localhost.localdomain> Fourthought, Inc. (http://Fourthought.com) announces the release of 4Suite 0.10.2 --------------------------- Open source tools for standards-based XML, DOM, XPath, XSLT, RDF XPointer, XLink and object-database development in Python http://4Suite.org 4Suite is a collection of Python tools for XML processing and object database management. An integrated packaging of several formerly separately-distributed components: 4DOM, 4XPath and 4XSLT, 4RDF, 4ODS, 4XPointer, 4XLink and DbDOM. News ---- * RDF: Added a driver based on shelve (DB/DBM) * ODS: Added a driver based on anydbm * Fix format-number support and implement in C * Improve Unicode and other encoding support * Documentation updates * Many misc optimizations * Many misc bug-fixes More info and Obtaining 4Suite ------------------------------ Please see http://4Suite.org From where you can download source, Windows and Linux binaries. 4Suite is distributed under a license similar to that of the Apache Web Server. -- Uche Ogbuji Principal Consultant uche.ogbuji@fourthought.com +01 303 583 9900 x 101 Fourthought, Inc. http://Fourthought.com 4735 East Walnut St, Ste. C, Boulder, CO 80301-2537, USA Software-engineering, knowledge-management, XML, CORBA, Linux, Python From uche.ogbuji@fourthought.com Fri Dec 1 11:19:35 2000 From: uche.ogbuji@fourthought.com (uche.ogbuji@fourthought.com) Date: Fri, 1 Dec 2000 04:19:35 -0700 Subject: [DB-SIG] ANN: 4Suite Server 0.10.0 Message-ID: <200012011119.EAA09896@localhost.localdomain> Fourthought, Inc. (http://Fourthought.com) announces the release of 4Suite Server 0.10.0 ---------------------------- An open source XML data server based on open standards implemented using 4Suite and other tools http://FourThought.com/4SuiteServer http://4Suite.org 4Suite Server is a platform for handling XML processing needs in application development. It is an XML data repository with a rules-based engine. It supports DOM access, XSLT transformation, XPath and RDF-based indexing and query, XLink resolution and many other XML services. It also supports other related services such as distributed transactions, and access control lists. It supports remote, cross-platform and cross-language access through CORBA and other request protocols to be added shortly. 4Suite Server is not designed to be a full-blown application server. It provides highly-specialized services for XML processing that can be used with other application servers. 4Suite Server is open-source and free to download. Priority support and customization is available from Fourthought, Inc. For more information on this, see the http://FourThought.com, or contact Fourthought at info@fourthought.com or +1 303 583 9900 The 4Suite Server home page is http://FourThought.com/4SuiteServer From where you can download the software itself or an executive summary thereof, read usage scenarios and find other information. From jonan-lists-python-db@callisia.com Sat Dec 2 00:10:15 2000 From: jonan-lists-python-db@callisia.com (Jonan Santiago) Date: Fri, 1 Dec 2000 19:10:15 -0500 Subject: [DB-SIG] Dumping Table Schema In-Reply-To: <20001201100705.P7343@glas.net>; from jno@glasnet.ru on Fri, Dec 01, 2000 at 10:07:05AM +0300 References: <20001130183802.A2079@sindri.callisia.com> <20001201100705.P7343@glas.net> Message-ID: <20001201191015.A13689@sindri.callisia.com> Thanks both for your tips. Just what I needed. Now I dont know why "select * from table where 1=0" works but it works! -Jonan Eugene V . Dvurechenski (jno@glasnet.ru) wrote: > i believe, the only _portable_ way is to > > 1) cursor.execute( "select * from table where 1=0" ) > 2) use cursor.description > > anything else is tightly bound to the specific DBMS (all those > SYS.ALL_* views in Oracle, for instance) > > -jno From gerhard@bigfoot.de Mon Dec 4 00:38:32 2000 From: gerhard@bigfoot.de (Gerhard =?iso-8859-1?Q?H=E4ring?=) Date: Mon, 04 Dec 2000 01:38:32 +0100 Subject: [DB-SIG] win32 build of MySQLdb-0.3.0 successful! Message-ID: <3A2AE788.39883BA9@bigfoot.de> Hi! I just wanted to drop you a note that your most recent version of MySQLdb builds just perfectly under win32 w/ distutils. I did some simple-minded stress test with the build and there were no problems. The original archive including the win32 files is available from my homepage, just on the front page. If you wish, you can just place them in your original archive. Windows users would then only have to issue "python setup.py install" to get a working version for win32. Finally, thank you very much for your effort on MySQLdb, this module was really helpful to me in the past. Gerhard -- contact: g e r h a r d @ b i g f o o t . d e web: http://highqualdev.com From andy@dustman.net Mon Dec 4 17:19:06 2000 From: andy@dustman.net (Andy Dustman) Date: Mon, 4 Dec 2000 12:19:06 -0500 (EST) Subject: [DB-SIG] Re: win32 build of MySQLdb-0.3.0 successful! In-Reply-To: <3A2AE788.39883BA9@bigfoot.de> Message-ID: On Mon, 4 Dec 2000, Gerhard [iso-8859-1] H=E4ring wrote: > Hi! >=20 > I just wanted to drop you a note that your most recent version of > MySQLdb builds just perfectly under win32 w/ distutils. I did some > simple-minded stress test with the build and there were no problems. The > original archive including the win32 files is available from my > homepage, just on the front page. If you wish, you can just place them > in your original archive. Windows users would then only have to issue > "python setup.py install" to get a working version for win32. I have linked to this, though I'll mention that if someone else wants to build a version for Python 1.5.2 (this one is for Python 2.0), I'll link to that as well. Also, if you could list the version of the MySQL client libraries that were used, that would help a lot. Probably best to use the latest 3.23 version for the client at this point. > Finally, thank you very much for your effort on MySQLdb, this module was > really helpful to me in the past. Thanks. --=20 Andy Dustman PGP: 0xC72F3F1D @ .net http://dustman.net/andy From paul@dubois.ws Tue Dec 5 14:18:12 2000 From: paul@dubois.ws (Paul DuBois) Date: Tue, 5 Dec 2000 08:18:12 -0600 Subject: [DB-SIG] Dumping Table Schema In-Reply-To: <20001201191015.A13689@sindri.callisia.com> References: <20001130183802.A2079@sindri.callisia.com> <20001201100705.P7343@glas.net> <20001201191015.A13689@sindri.callisia.com> Message-ID: At 7:10 PM -0500 12/1/00, Jonan Santiago wrote: >Thanks both for your tips. Just what I needed. Now I dont know >why "select * from table where 1=0" works but it works! Per the original question, my understanding (from some discussion a while back on the DBI mailing list) is that this actually isn't completely portable. Although it works for many database engines, it doesn't work for all. Sorry, don't know any examples where it doesn't work. I do know it does work for MySQL. > >-Jonan > >Eugene V . Dvurechenski (jno@glasnet.ru) wrote: >> i believe, the only _portable_ way is to >> >> 1) cursor.execute( "select * from table where 1=0" ) >> 2) use cursor.description >> >> anything else is tightly bound to the specific DBMS (all those >> SYS.ALL_* views in Oracle, for instance) >> >> -jno > >_______________________________________________ >DB-SIG maillist - DB-SIG@python.org >http://www.python.org/mailman/listinfo/db-sig From mal@lemburg.com Tue Dec 5 16:53:31 2000 From: mal@lemburg.com (M.-A. Lemburg) Date: Tue, 05 Dec 2000 17:53:31 +0100 Subject: [DB-SIG] Dumping Table Schema References: <20001130183802.A2079@sindri.callisia.com> <20001201100705.P7343@glas.net> <20001201191015.A13689@sindri.callisia.com> Message-ID: <3A2D1D8B.79DE0A23@lemburg.com> Paul DuBois wrote: > > At 7:10 PM -0500 12/1/00, Jonan Santiago wrote: > >Thanks both for your tips. Just what I needed. Now I dont know > >why "select * from table where 1=0" works but it works! > > Per the original question, my understanding (from some discussion a > while back on the DBI mailing list) is that this actually isn't > completely portable. Although it works for many database engines, it > doesn't work for all. Sorry, don't know any examples where it doesn't > work. I do know it does work for MySQL. FYI, It works for mxODBC too (and all supported database backends). The only thing to watch out for whether or not the column names include the table name or not and whether they are case sensitive or not. Note that in mxODBC you can also use the catalog methods to get some more information about the database schema from the database. These map to ODBC calls which translate the request into the database specific versions. > > > >-Jonan > > > >Eugene V . Dvurechenski (jno@glasnet.ru) wrote: > >> i believe, the only _portable_ way is to > >> > >> 1) cursor.execute( "select * from table where 1=0" ) > >> 2) use cursor.description > >> > >> anything else is tightly bound to the specific DBMS (all those > >> SYS.ALL_* views in Oracle, for instance) > >> > >> -jno > > > >_______________________________________________ > >DB-SIG maillist - DB-SIG@python.org > >http://www.python.org/mailman/listinfo/db-sig > > _______________________________________________ > DB-SIG maillist - DB-SIG@python.org > http://www.python.org/mailman/listinfo/db-sig -- Marc-Andre Lemburg ______________________________________________________________________ Company: http://www.egenix.com/ Consulting: http://www.lemburg.com/ Python Pages: http://www.lemburg.com/python/ From frank63@ms5.hinet.net Wed Dec 6 02:41:53 2000 From: frank63@ms5.hinet.net (Frank J.S. Chen) Date: Wed, 6 Dec 2000 02:41:53 -0000 Subject: [DB-SIG] Persistence Message-ID: <200012051841.CAA11990@ms5.hinet.net> Hi, Is that possible to put a Python object into a relational database? ---------------------------------------------------------------------------- ------- Chen Chien-Hsun Taipei,Taiwan,R.O.C. From mal@lemburg.com Tue Dec 5 19:01:56 2000 From: mal@lemburg.com (M.-A. Lemburg) Date: Tue, 05 Dec 2000 20:01:56 +0100 Subject: [DB-SIG] Persistence References: <200012051841.CAA11990@ms5.hinet.net> Message-ID: <3A2D3BA4.EE7400F8@lemburg.com> "Frank J.S. Chen" wrote: > > Hi, > > Is that possible to put a Python object into a relational database? Sure, you only have to pass it through the Python pickle module and then store it in a varchar() or blob. -- Marc-Andre Lemburg ______________________________________________________________________ Company: http://www.egenix.com/ Consulting: http://www.lemburg.com/ Python Pages: http://www.lemburg.com/python/ From djc@object-craft.com.au Tue Dec 5 22:47:25 2000 From: djc@object-craft.com.au (Dave Cole) Date: 06 Dec 2000 09:47:25 +1100 Subject: [DB-SIG] Dumping Table Schema In-Reply-To: Paul DuBois's message of "Tue, 5 Dec 2000 08:18:12 -0600" References: <20001130183802.A2079@sindri.callisia.com> <20001201100705.P7343@glas.net> <20001201191015.A13689@sindri.callisia.com> Message-ID: >>>>> "Paul" == Paul DuBois writes: Paul> At 7:10 PM -0500 12/1/00, Jonan Santiago wrote: >> Thanks both for your tips. Just what I needed. Now I dont know why >> "select * from table where 1=0" works but it works! Paul> Per the original question, my understanding (from some Paul> discussion a while back on the DBI mailing list) is that this Paul> actually isn't completely portable. Although it works for many Paul> database engines, it doesn't work for all. Sorry, don't know Paul> any examples where it doesn't work. I do know it does work for Paul> MySQL. It also works for my Sybase module. http://www.object-craft.com.au/projects/sybase/ - Dave -- http://www.object-craft.com.au From Mike.Olson@fourthought.com Fri Dec 8 21:11:58 2000 From: Mike.Olson@fourthought.com (Mike Olson) Date: Fri, 08 Dec 2000 14:11:58 -0700 Subject: [DB-SIG] Persistence References: <200012051841.CAA11990@ms5.hinet.net> Message-ID: <3A314E9E.B0BC043A@FourThought.com> "Frank J.S. Chen" wrote: > > Hi, > > Is that possible to put a Python object into a relational database? Have you looked into 4ODS? It allows you to specify persistent attributes on an object, then generates persistent base classes for you to use as python objects. As these objects are created, modified, etc. 4ODS updates the relational backend for you. It can be found at http://4Suite.org/ in the 4Suite distribution. Mike > > ---------------------------------------------------------------------------- > ------- > Chen Chien-Hsun > Taipei,Taiwan,R.O.C. > > _______________________________________________ > DB-SIG maillist - DB-SIG@python.org > http://www.python.org/mailman/listinfo/db-sig -- Mike Olson Principal Consultant mike.olson@fourthought.com (303)583-9900 x 102 Fourthought, Inc. http://Fourthought.com Software-engineering, knowledge-management, XML, CORBA, Linux, Python From mal@lemburg.com Fri Dec 15 22:59:58 2000 From: mal@lemburg.com (M.-A. Lemburg) Date: Fri, 15 Dec 2000 23:59:58 +0100 Subject: [DB-SIG] Databases and Unicode Message-ID: <3A3AA26E.2E24ECCA@lemburg.com> Hi everybody, I'm currently looking into adding Unicode support to mxODBC and was wondering about the best way to add it (I'm also thinking about an extension to the DB API). Here are some possibilities: 1. enable the support using a compile time switch 2. enable the support on a per-connection basis 3. enable the support on a per-cursor basis I already have an experimental version of 1. Thoughts ? An a related topic: what would you consider the best way to implement column type binding and output conversion APIs ? Do any of the DB API module authors have experience with this ? Thanks, -- Marc-Andre Lemburg ______________________________________________________________________ Company: http://www.egenix.com/ Consulting: http://www.lemburg.com/ Python Pages: http://www.lemburg.com/python/ From Sharriff.Aina@med-iq.de Tue Dec 19 12:36:47 2000 From: Sharriff.Aina@med-iq.de (Sharriff.Aina@med-iq.de) Date: Tue, 19 Dec 2000 12:36:47 +0000 Subject: [DB-SIG] MySQLdb Message-ID: Hi List! I=B4m new to both Python and MySQLdb, is there some kind person out the= re that can guide me through the process of installing the MySQLdb library= on windows? my python path is fine, when I run "setup.py", I get an "no commands supplied" error . Thanks for your anticipated help Sharriff Aina = From manyong@gnu.org Wed Dec 20 09:47:39 2000 From: manyong@gnu.org (Man-Yong Lee) Date: Wed, 20 Dec 2000 18:47:39 +0900 Subject: [DB-SIG] IBM DB2 module v0.97 References: <20001219170102.6BD02E96E@mail.python.org> Message-ID: <3A40803B.229F3535@gnu.org> Hi~ db-sig people, I've just released IBM DB2 module v0.97 for Python now. Hopefully, BLOB and CLOB is supported with reasonable usage like these: cs.execute("INSERT INTO HJ0 VALUES (?)", \ DB2.BLOB('/bin/bash')) clob = DB2.CLOB() clob.setValue('A' * 1024) cs.execute("INSERT INTO HJ1 VALUES (?, ?)", \ ( 1, clob ) ) And you get BLOB, CLOB instance when you fetch rows: cs.execute("SELECT * FROM HJ0 FETCH FIRST 1 ROW ONLY") cs.fetchone() --> (DB2.BLOB(....), ) You can get data in Python string with getValue() method. The download site is: ftp://people.linuxkorea.co.kr/pub/DB2/ Thanks to the people who sent me bug reports. TODO: - DATE, TIME, TIMESTAMP class for seamlese integration with Python. - DBLOB support -- Happy Python! Man-Yong (Bryan) Lee From ryanw@inktomi.com Thu Dec 21 01:17:34 2000 From: ryanw@inktomi.com (Ryan Weisenberger) Date: Wed, 20 Dec 2000 17:17:34 -0800 Subject: [DB-SIG] Problems with MySQL Message-ID: <4.3.2.7.2.20001220170813.00aeda70@inkt-3.inktomi.com> I'm trying to install and use the MySQL module written by Andy Dustman. I'm using version 0.3.0, with Python 2.0 and MySQL 3.23 on Redhat Linux 6.2. It compiles fine, but when I try: db1 = MySQLdb.Connect(db='test') I get a SIGSEGV and a core dump. Running it under gdb, I can trace it down to _mysqlmodule.c: conn = mysql_real_connect(&(c->connection), host, user, passwd, db, port, unix_socket, client_flag); All the values look good going in, but that's where it explodes. Has anyone encountered this or have any solutions? Thanks, Ryan From mal@lemburg.com Thu Dec 21 11:20:13 2000 From: mal@lemburg.com (M.-A. Lemburg) Date: Thu, 21 Dec 2000 12:20:13 +0100 Subject: [DB-SIG] Problems with MySQL References: <4.3.2.7.2.20001220170813.00aeda70@inkt-3.inktomi.com> Message-ID: <3A41E76D.12E1176A@lemburg.com> Ryan Weisenberger wrote: > > I'm trying to install and use the MySQL module written by Andy > Dustman. I'm using version 0.3.0, with Python 2.0 and MySQL 3.23 on Redhat > Linux 6.2. It compiles fine, but when I try: > db1 = MySQLdb.Connect(db='test') > I get a SIGSEGV and a core dump. > > Running it under gdb, I can trace it down to _mysqlmodule.c: > conn = mysql_real_connect(&(c->connection), host, user, passwd, db, > port, unix_socket, client_flag); > > All the values look good going in, but that's where it explodes. > > Has anyone encountered this or have any solutions? Is the MySQL version you are using compatible with the MySQLdb version ? Are both compiled using the same compiler ? MySQL is a complete mess when it comes to finding working combinations of server, client libs and third party tools which actually work as advertised... -- Marc-Andre Lemburg ______________________________________________________________________ Company: http://www.egenix.com/ Consulting: http://www.lemburg.com/ Python Pages: http://www.lemburg.com/python/ From coupet00" Hi I've been struggling to build extensions from installation instructions.The goal was to produce a working Oracle 8 interface for Python for Windows. I'm sure that there must be load-and-go binaries out there, but all I can find are tempting (and necessary) extensions, which are just beyond my reach, and that of my team. I come from a Delphi background, and have found that Python is indeed the "best thing since sliced bread" as far as development languages go. However, I've experienced days of frustration as the product requires me to become an extension builder if I want to access an Oracle system from windows, say - surely there's a standard set of ODBC drivers that exist in binary form for Windows? Then I find that the installation instructions don't handle exceptions well - in other words, if the build result isn't what the installation instructions say, then one is stuck! Presumably, I am not unique in this respect, but represent a class of developer for whom Python should be a natural progression (ie application developers and architects). However, one can't go very far in applications without database interfaces. Or maybe my expectations of Python is wrong. I'd be interested if others have had the same experience, and what they did to move on... Thanks Tim Dr Tim Couper From mal@lemburg.com Thu Dec 21 13:16:31 2000 From: mal@lemburg.com (M.-A. Lemburg) Date: Thu, 21 Dec 2000 14:16:31 +0100 Subject: [DB-SIG] frustrations of extension building References: <000801c06b47$67d75830$b0b5888b@ha.uk.sbphrd.com> Message-ID: <3A4202AF.A8BE80EE@lemburg.com> coupet00 wrote: > > Hi > > I've been struggling to build extensions from installation instructions.The > goal was to produce a working Oracle 8 interface for Python for Windows. I'm > sure that there must be load-and-go binaries out there, but all I can find > are tempting (and necessary) extensions, which are just beyond my reach, and > that of my team. > > I come from a Delphi background, and have found that Python is indeed the > "best thing since sliced bread" as far as development languages go. However, > I've experienced days of frustration as the product requires me to become an > extension builder if I want to access an Oracle system from windows, say - > surely there's a standard set of ODBC drivers that exist in binary form for > Windows? You might consider switching to mxODBC which comes with a precompiled binary for Windows. mxODBC is available from my Python Pages (see sig). > Then I find that the installation instructions don't handle > exceptions well - in other words, if the build result isn't what the > installation instructions say, then one is stuck! > > Presumably, I am not unique in this respect, but represent a class of > developer for whom Python should be a natural progression (ie application > developers and architects). However, one can't go very far in applications > without database interfaces. Or maybe my expectations of Python is wrong. > > I'd be interested if others have had the same experience, and what they did > to move on... > > Thanks > > Tim > > Dr Tim Couper > > _______________________________________________ > DB-SIG maillist - DB-SIG@python.org > http://www.python.org/mailman/listinfo/db-sig -- Marc-Andre Lemburg ______________________________________________________________________ Company: http://www.egenix.com/ Consulting: http://www.lemburg.com/ Python Pages: http://www.lemburg.com/python/ From paul@dubois.ws Thu Dec 21 20:52:34 2000 From: paul@dubois.ws (Paul DuBois) Date: Thu, 21 Dec 2000 14:52:34 -0600 Subject: [DB-SIG] Problems with MySQL In-Reply-To: <4.3.2.7.2.20001220170813.00aeda70@inkt-3.inktomi.com> References: <4.3.2.7.2.20001220170813.00aeda70@inkt-3.inktomi.com> Message-ID: At 5:17 PM -0800 12/20/00, Ryan Weisenberger wrote: >I'm trying to install and use the MySQL module written by Andy >Dustman. I'm using version 0.3.0, with Python 2.0 and MySQL 3.23 on >Redhat Linux 6.2. It compiles fine, but when I try: >db1 = MySQLdb.Connect(db='test') >I get a SIGSEGV and a core dump. > >Running it under gdb, I can trace it down to _mysqlmodule.c: >conn = mysql_real_connect(&(c->connection), host, user, passwd, db, > port, unix_socket, client_flag); > >All the values look good going in, but that's where it explodes. > >Has anyone encountered this or have any solutions? > >Thanks, >Ryan What's your *exact* MySQL server version? I just updated to MySQL 3.23.29a-gamma, and found that the "a" caused MySQLdb 0.3.0 to cough at the code that splits the three numeric hunks out of the version string. (Normally versions are n.nn.nn-xxxx, where n is a digit.) I find that this fixes the problem (split on dots, strip non-digit stuff from third component): --- MySQLdb.py.orig Tue Oct 31 13:51:19 2000 +++ MySQLdb.py Thu Dec 21 14:47:23 2000 @@ -454,7 +454,9 @@ self.db = apply(connect, (), kwargs) self.quote_conv[types.StringType] = self.Thing2Literal self._server_info = self.db.get_server_info() - i = map(int, split(split(self._server_info, '-')[0],'.')) + i = split(self._server_info,'.') + i[2] = re.sub('\D*$','',i[2]) + i = map(int, i); self._server_version = i[0]*10000 + i[1]*100 + i[2] if _threading: self.__lock = _threading.Lock() However, my scripts weren't core dumping, they just exited with a stack trace, so this may not be your problem. I too am running MySQLdb 0.3.0 and RedHat 6.2, but I'm still running Python 1.5.1. From andy@dustman.net Thu Dec 21 22:04:50 2000 From: andy@dustman.net (Andy Dustman) Date: Thu, 21 Dec 2000 17:04:50 -0500 (EST) Subject: [DB-SIG] Problems with MySQL In-Reply-To: Message-ID: On Thu, 21 Dec 2000, Paul DuBois wrote: > At 5:17 PM -0800 12/20/00, Ryan Weisenberger wrote: > >I'm trying to install and use the MySQL module written by Andy > >Dustman. I'm using version 0.3.0, with Python 2.0 and MySQL 3.23 on > >Redhat Linux 6.2. It compiles fine, but when I try: > >db1 = MySQLdb.Connect(db='test') > >I get a SIGSEGV and a core dump. > > > >Running it under gdb, I can trace it down to _mysqlmodule.c: > >conn = mysql_real_connect(&(c->connection), host, user, passwd, db, > > port, unix_socket, client_flag); > > > >All the values look good going in, but that's where it explodes. I haven't seen or heard of MySQLdb dumping core in a long time. For it to die where it is points a bit to MySQL, but I would be interested in seeing what the parameter values are. A lot of them CAN be NULL (most of the strings). > What's your *exact* MySQL server version? I just updated to MySQL > 3.23.29a-gamma, and found that the "a" caused MySQLdb 0.3.0 to cough > at the code that splits the three numeric hunks out of the version string. > (Normally versions are n.nn.nn-xxxx, where n is a digit.) I which those MySQL people could make up their minds about what the format of the version string is going to be. -- Andy Dustman PGP: 0xC72F3F1D @ .net http://dustman.net/andy From adustman@comstar.net Thu Dec 21 22:08:12 2000 From: adustman@comstar.net (Andy Dustman) Date: Thu, 21 Dec 2000 17:08:12 -0500 (EST) Subject: [DB-SIG] MySQLdb In-Reply-To: Message-ID: On Tue, 19 Dec 2000 Sharriff.Aina@med-iq.de wrote: > Hi List! >=20 > I=B4m new to both Python and MySQLdb, is there some kind person out there > that can guide me through the process of installing the MySQLdb library o= n > windows? my python path is fine, when I run "setup.py", I get an "no > commands supplied" error . Try: python setup.py install --=20 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,=20 come no further, for death awaits you all, with nasty, big, pointy teeth!" From ryanw@inktomi.com Thu Dec 21 22:29:41 2000 From: ryanw@inktomi.com (Ryan Weisenberger) Date: Thu, 21 Dec 2000 14:29:41 -0800 Subject: [DB-SIG] Problems with MySQL In-Reply-To: References: Message-ID: <4.3.2.7.2.20001221142433.00c496d0@inkt-3.inktomi.com> Exact version of MySQL is 3.23.28. Although I found that if I downgraded MySQL to 3.22.32, I can actually get the MySQLdb.Connect to work, and instead it core dumps on the cursor.execute statement. But it looks like this may be a Python 2.0 problem. It compiles and runs fine under Python 1.5.2. Thanks Paul for the tip about the version number. I'll watch out for that. - Ryan At 05:04 PM 12/21/00 -0500, you wrote: >On Thu, 21 Dec 2000, Paul DuBois wrote: > > > At 5:17 PM -0800 12/20/00, Ryan Weisenberger wrote: > > >I'm trying to install and use the MySQL module written by Andy > > >Dustman. I'm using version 0.3.0, with Python 2.0 and MySQL 3.23 on > > >Redhat Linux 6.2. It compiles fine, but when I try: > > >db1 = MySQLdb.Connect(db='test') > > >I get a SIGSEGV and a core dump. > > > > > >Running it under gdb, I can trace it down to _mysqlmodule.c: > > >conn = mysql_real_connect(&(c->connection), host, user, passwd, db, > > > port, unix_socket, client_flag); > > > > > >All the values look good going in, but that's where it explodes. > >I haven't seen or heard of MySQLdb dumping core in a long time. For it to >die where it is points a bit to MySQL, but I would be interested in seeing >what the parameter values are. A lot of them CAN be NULL (most of the >strings). > > > What's your *exact* MySQL server version? I just updated to MySQL > > 3.23.29a-gamma, and found that the "a" caused MySQLdb 0.3.0 to cough > > at the code that splits the three numeric hunks out of the version string. > > (Normally versions are n.nn.nn-xxxx, where n is a digit.) > >I which those MySQL people could make up their minds about what the format >of the version string is going to be. > >-- >Andy Dustman PGP: 0xC72F3F1D > @ .net http://dustman.net/andy From andy@dustman.net Thu Dec 21 22:42:54 2000 From: andy@dustman.net (Andy Dustman) Date: Thu, 21 Dec 2000 17:42:54 -0500 (EST) Subject: [DB-SIG] Problems with MySQL In-Reply-To: <4.3.2.7.2.20001221142433.00c496d0@inkt-3.inktomi.com> Message-ID: On Thu, 21 Dec 2000, Ryan Weisenberger wrote: > Exact version of MySQL is 3.23.28. Although I found that if I downgraded > MySQL to 3.22.32, I can actually get the MySQLdb.Connect to work, and > instead it core dumps on the cursor.execute statement. > > But it looks like this may be a Python 2.0 problem. It compiles and runs > fine under Python 1.5.2. I know you are using Red Hat 6.2. I assume it's an Intel platform. I have not done a lot of testing with Python 2.0 yet. Are you using the precompiled MySQL RPMs from mysql.com, or rolling your own? -- Andy Dustman PGP: 0xC72F3F1D @ .net http://dustman.net/andy From ryanw@inktomi.com Thu Dec 21 22:48:48 2000 From: ryanw@inktomi.com (Ryan Weisenberger) Date: Thu, 21 Dec 2000 14:48:48 -0800 Subject: [DB-SIG] Problems with MySQL In-Reply-To: References: <4.3.2.7.2.20001221142433.00c496d0@inkt-3.inktomi.com> Message-ID: <4.3.2.7.2.20001221144609.00af1230@inkt-3.inktomi.com> I'm using the tarball of the binaries from mysql.com. Redhat Linux 6.2 on Intel. - Ryan At 05:42 PM 12/21/00 -0500, you wrote: >On Thu, 21 Dec 2000, Ryan Weisenberger wrote: > > > Exact version of MySQL is 3.23.28. Although I found that if I downgraded > > MySQL to 3.22.32, I can actually get the MySQLdb.Connect to work, and > > instead it core dumps on the cursor.execute statement. > > > > But it looks like this may be a Python 2.0 problem. It compiles and runs > > fine under Python 1.5.2. > >I know you are using Red Hat 6.2. I assume it's an Intel platform. I have >not done a lot of testing with Python 2.0 yet. Are you using the >precompiled MySQL RPMs from mysql.com, or rolling your own? > >-- >Andy Dustman PGP: 0xC72F3F1D > @ .net http://dustman.net/andy _________________________ Ryan Weisenberger Software Developer ryanw@inktomi.com (650) 653-4595 _________________________ From andy@dustman.net Thu Dec 21 22:56:00 2000 From: andy@dustman.net (Andy Dustman) Date: Thu, 21 Dec 2000 17:56:00 -0500 (EST) Subject: [DB-SIG] Problems with MySQL In-Reply-To: <4.3.2.7.2.20001221144609.00af1230@inkt-3.inktomi.com> Message-ID: On Thu, 21 Dec 2000, Ryan Weisenberger wrote: > I'm using the tarball of the binaries from mysql.com. Redhat Linux 6.2 on > Intel. I've been using the RPMs, myself, but lately with Red Hat 7.0. I tend to think that _mysqlmodule.c must be doing something in the module initialization that is bogus with Python 2.0. Don't know what, though... -- Andy Dustman PGP: 0xC72F3F1D @ .net http://dustman.net/andy From bangmin@NOTENHILL.com Fri Dec 22 03:40:57 2000 From: bangmin@NOTENHILL.com (=?euc-kr?B?uea5zg==?=) Date: Fri, 22 Dec 2000 12:40:57 +0900 Subject: [DB-SIG] [[DCOracle] cannot open shared object file: No such file or direc tory Message-ID: Hi, there. i'm totally beat with this stuff. --; please give me a hand. i got the right result when i run it on command prompt(bash). but as a apache cgi, it just print error messages below. here's my source(very simple..) -------------------------------------------------------------- #! /usr/bin/python import sys sys.path.append('/home/oracle/OraHome1/lib') import sys import DCOracle print 'content-type: text/html\n' print print 'DCOracle imported' print sys.path ------------------------------------------------------------ and it's error message(from apache/logs/error_log) : ------------------------------------------------------------ Traceback (innermost last): File "/usr/local/apache/cgi-bin/List22.py", line 7, in ? import DCOracle File "DCOracle/__init__.py", line 66, in ? File "DCOracle/ocidb.py", line 50, in ? ImportError: libclntsh.so.8.0: cannot open shared object file: No such file or directory ------------------------------------------------------------ Apache was compiled with --enable-module=so, I confirmed ORACLE_BASE, ORACLE_HOME, LD_LIBRARY_PATH, PATH, and PYTHONPATH Python version is 1.5.2 DCOracle version is 1.3.2 Apache version is 1.3.14 OS : RH Linux 6.2 need more info? just let me know. Thanks in advance. Min. From djc@object-craft.com.au Fri Dec 22 05:13:42 2000 From: djc@object-craft.com.au (Dave Cole) Date: 22 Dec 2000 16:13:42 +1100 Subject: [DB-SIG] Sybase module 0.10 released Message-ID: What is it: The Sybase module provides a Python interface to the Sybase relational database system. The Sybase package supports almost all of the Python Database API, version 2.0 with extensions. The module works with Python versions 1.5.2 and later and Sybase versions 11.0.3 and later. It is based on the Sybase Client Library (ct_* API), and the Bulk-Library Client (blk_* API) interfaces. Changes: - The numeric object has been reimplemented using the cs_convert/cs_calc/cs_cmp API. This has improved the coerce behaviour over the previous release. >>> import Sybase >>> n = Sybase.numeric(100200300400500L) >>> n / 12.3456 8116276276608.6702954898911353032659409020 >>> n / Sybase.numeric('12.3456') 8116276276608.67029548989113530326 >>> n.precision, n.scale (15, 0) >>> n + 12.3456 100200300400512.345600000000 >>> n + Sybase.numeric('12.3456') 100200300400512.3456 >>> n.precision, n.scale (15, 0) You can also specify a precision and scale in the constructor. >>> m = Sybase.numeric(n, 30, 2) >>> m 100200300400500.00 >>> m.precision, m.scale (30, 2) Where can you get it: http://www.object-craft.com.au/projects/sybase/ - Dave -- http://www.object-craft.com.au From lane@cycletime.com Fri Dec 22 05:16:20 2000 From: lane@cycletime.com (Lane Stevens) Date: Thu, 21 Dec 2000 22:16:20 -0700 Subject: [DB-SIG] [[DCOracle] cannot open shared object file: No such file or direc tory In-Reply-To: ; from bangmin@NOTENHILL.com on Fri, Dec 22, 2000 at 12:40:57PM +0900 References: Message-ID: <20001221221620.A3078@stel02-linux.corp.rmi.net> Have you set the LD_LIBRARY_PATH in the httpd.conf file so that Apache exports the proper environment when it launches the cgi script? Thanks, Lane. On Fri, Dec 22, 2000 at 12:40:57PM +0900, ¹æ¹Î wrote: > Hi, there. > > i'm totally beat with this stuff. --; please give me a hand. > > i got the right result when i run it on command prompt(bash). > but as a apache cgi, it just print error messages below. > > here's my source(very simple..) > -------------------------------------------------------------- > #! /usr/bin/python > > > import sys > sys.path.append('/home/oracle/OraHome1/lib') > import sys > import DCOracle > print 'content-type: text/html\n' > print > print 'DCOracle imported' > print sys.path > ------------------------------------------------------------ > > and it's error message(from apache/logs/error_log) : > ------------------------------------------------------------ > Traceback (innermost last): > File "/usr/local/apache/cgi-bin/List22.py", line 7, in ? > import DCOracle > File "DCOracle/__init__.py", line 66, in ? > File "DCOracle/ocidb.py", line 50, in ? > ImportError: libclntsh.so.8.0: cannot open shared object file: No such file > or directory > ------------------------------------------------------------ > > Apache was compiled with --enable-module=so, > I confirmed ORACLE_BASE, ORACLE_HOME, LD_LIBRARY_PATH, PATH, and PYTHONPATH > > Python version is 1.5.2 > DCOracle version is 1.3.2 > Apache version is 1.3.14 > OS : RH Linux 6.2 > > need more info? just let me know. > > Thanks in advance. > > Min. > > _______________________________________________ > DB-SIG maillist - DB-SIG@python.org > http://www.python.org/mailman/listinfo/db-sig -- Lane Stevens Terrapin Technologies, Inc. http://www.cycletime.com From djc@object-craft.com.au Sat Dec 23 06:34:16 2000 From: djc@object-craft.com.au (Dave Cole) Date: 23 Dec 2000 17:34:16 +1100 Subject: [DB-SIG] Sybase module 0.11 (Sam Rushing release) released Message-ID: What is it: The Sybase module provides a Python interface to the Sybase relational database system. The Sybase package supports almost all of the Python Database API, version 2.0 with extensions. The module works with Python versions 1.5.2 and later and Sybase versions 11.0.3 and later. It is based on the Sybase Client Library (ct_* API), and the Bulk-Library Client (blk_* API) interfaces. Changes: - The hashing of numeric objects has been fixed to generate the same hash values as a Python int / long of the same value. Thanks to Sam Rushing for helping with this. >>> import Sybase >>> hash(100) 100 >>> hash(Sybase.numeric(100)) 100 >>> hash(10000000000000000L) 1877247730 >>> hash(Sybase.numeric(10000000000000000L)) 1877247730 Hash of a float value does not match. >>> hash(Sybase.numeric(100.2)) -1654341571 >>> hash(100.2) -1717999926 Where can you get it: http://www.object-craft.com.au/projects/sybase/ - Dave -- http://www.object-craft.com.au