From info at egenix.com Tue Sep 1 21:11:53 2009 From: info at egenix.com (eGenix Team: M.-A. Lemburg) Date: Tue, 01 Sep 2009 21:11:53 +0200 Subject: [DB-SIG] ANN: eGenix mxODBC - Python ODBC Database Interface 3.0.3 Message-ID: <4A9D71F9.9030503@egenix.com> ________________________________________________________________________ ANNOUNCING eGenix.com mxODBC - Python ODBC Database Interface Version 3.0.3 mxODBC is our commercially supported Python extension providing ODBC database connectivity to Python applications on Windows and Unix platforms This announcement is also available on our web-site for online reading: http://www.egenix.com/company/news/eGenix-mxODBC-3.0.3-GA.html ________________________________________________________________________ INTRODUCTION mxODBC provides an easy-to-use, high-performance, reliable and robust Python interface to ODBC compatible databases such as MS SQL Server, MS Access, Oracle Database, IBM DB2 and Informix , Sybase ASE and Sybase Anywhere, MySQL, PostgreSQL, SAP MaxDB and many more. The "eGenix mxODBC - Python ODBC Database Interface" product is a commercial extension to our open-source eGenix mx Base Distribution. * About Python (http://www.python.org/): Python is an object-oriented Open Source programming language which runs on all modern platforms. By integrating ease-of-use, clarity in coding, enterprise application connectivity and rapid application design, Python establishes an ideal programming platform for today's IT challenges. * About eGenix (http://www.egenix.com/): eGenix is a software project, consulting and product company focusing on expert services and professional quality products for companies, Python users and developers. ________________________________________________________________________ NEWS mxODBC 3.0.3 is a patch-level release and includes the following updates: * Python 2.3 - 2.6 support: mxODBC 3.0 is available for Python 2.3, 2.4, 2.5 and 2.6. We ship binaries for Windows, Linux, Mac OS X, AIX, Solaris, and offer custom porting services for most other platforms. * Enhanced support for using cursors as iterators: mxODBC cursor objects can now be used as iterators to iterate over result sets. While this was already possible in previous versions using wrappers, we have now added direct iterator support to the cursor objects themselves. * Updated work-arounds for various ODBC drivers: eGenix always aims to make using mxODBC as easy and robust as possible. For this reason, we regularly add or update work-arounds for problems found in recent ODBC driver versions. This release includes new work-arounds for the MySQL ODBC driver running on 64-bit Linux, the SQL Server 200 ODBC driver and the FileMaker ODBC driver. For the full set of changes please check the mxODBC change log: http://www.egenix.com/products/python/mxODBC/changelog.html For the full set of features mxODBC has to offer, please see: http://www.egenix.com/products/python/mxODBC/#Features ________________________________________________________________________ DOWNLOADS The download archives and instructions for installing the package can be found at: http://www.egenix.com/products/python/mxODBC/ In order to use the eGenix mxODBC package you will first need to install the eGenix mx Base package: http://www.egenix.com/products/python/mxBase/ ________________________________________________________________________ UPGRADING You are encouraged to upgrade to this latest mxODBC release, especially if you are using MS SQL Server or Informix as database server. Customers who have purchased mxODBC 3.0 licenses can download and install this patch-level release on top of their existing installations. The licenses will continue to work with version 3.0.2. Users of mxODBC 2.0 will have to purchase new licenses from our online shop in order to upgrade to mxODBC 3.0.2. You can request 30-day evaluation licenses by visiting our web-site at http://www.egenix.com/products/python/mxODBC/#Evaluation or writing to sales at egenix.com, stating your name (or the name of the company) and the number of eval licenses that you need. _______________________________________________________________________ SUPPORT Commercial support for this product is available from eGenix.com. Please see http://www.egenix.com/services/support/ for details about our support offerings. Enjoy, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Sep 01 2009) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ From srlopez at policlinicagipuzkoa.com Mon Sep 7 17:38:47 2009 From: srlopez at policlinicagipuzkoa.com (santi1) Date: Mon, 7 Sep 2009 08:38:47 -0700 (PDT) Subject: [DB-SIG] How to connect to informix DB in an easy way In-Reply-To: <25076131.post@talk.nabble.com> References: <25076131.post@talk.nabble.com> Message-ID: <25332401.post@talk.nabble.com> Provably, now you has solve the problem. In windows download 'InformixDB-2.5.win32-py2.5.exe', and install. Then the code is easy, i used this for reading BLOBS. Dont forget to install InformixConnect and setup the variables for Host and server . import sys import informixdb import os conn = informixdb.connect('database at server', 'user', 'password') cursor = conn.cursor(rowformat = informixdb.ROW_AS_DICT) cursor.execute("SELECT * FROM blobtable WHERE handle=457034") f=open('file.doc', 'wb+') for row in cursor: f.write(row['contenido']) f.close() cmd = 'file.doc' os.system(cmd) conn.commit() conn.close() sys.exit(0) -- View this message in context: http://www.nabble.com/How-to-connect-to-informix-DB-in-an-easy-way-tp25076131p25332401.html Sent from the Python - db-sig mailing list archive at Nabble.com. From phd at phd.pp.ru Sun Sep 20 21:13:19 2009 From: phd at phd.pp.ru (Oleg Broytmann) Date: Sun, 20 Sep 2009 23:13:19 +0400 Subject: [DB-SIG] SQLObject 0.10.7 Message-ID: <20090920191319.GC8326@phd.pp.ru> Hello! I'm pleased to announce version 0.10.7, a minor bugfix release of 0.10 branch of SQLObject. What is SQLObject ================= SQLObject is an object-relational mapper. Your database tables are described as classes, and rows are instances of those classes. SQLObject is meant to be easy to use and quick to get started with. SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite, Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB). Where is SQLObject ================== Site: http://sqlobject.org Development: http://sqlobject.org/devel/ Mailing list: https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss Archives: http://news.gmane.org/gmane.comp.python.sqlobject Download: http://cheeseshop.python.org/pypi/SQLObject/0.10.7 News and changes: http://sqlobject.org/News.html What's New ========== News since 0.10.6 ----------------- * Fixed a bug: Sybase tables with identity column fire two identity_inserts. * Fixed a bug: q.startswith(), q.contains() and q.endswith() escape (with a backslash) all special characters (backslashes, underscores and percent signs). For a more complete list, please see the news: http://sqlobject.org/News.html Oleg. -- Oleg Broytmann http://phd.pp.ru/ phd at phd.pp.ru Programmers don't die, they just GOSUB without RETURN. From phd at phd.pp.ru Sun Sep 20 21:20:35 2009 From: phd at phd.pp.ru (Oleg Broytmann) Date: Sun, 20 Sep 2009 23:20:35 +0400 Subject: [DB-SIG] SQLObject 0.11.1 Message-ID: <20090920192035.GG8326@phd.pp.ru> Hello! I'm pleased to announce version 0.11.1, a minor bugfix release of 0.11 branch of SQLObject. What is SQLObject ================= SQLObject is an object-relational mapper. Your database tables are described as classes, and rows are instances of those classes. SQLObject is meant to be easy to use and quick to get started with. SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite, Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB). Where is SQLObject ================== Site: http://sqlobject.org Development: http://sqlobject.org/devel/ Mailing list: https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss Archives: http://news.gmane.org/gmane.comp.python.sqlobject Download: http://cheeseshop.python.org/pypi/SQLObject/0.11.1 News and changes: http://sqlobject.org/News.html What's New ========== News since 0.11.0 ----------------- * Fixed a bug: Sybase tables with identity column fire two identity_inserts. * Fixed a bug: q.startswith(), q.contains() and q.endswith() escape (with a backslash) all special characters (backslashes, underscores and percent signs). For a more complete list, please see the news: http://sqlobject.org/News.html Oleg. -- Oleg Broytmann http://phd.pp.ru/ phd at phd.pp.ru Programmers don't die, they just GOSUB without RETURN. From vernondcole at gmail.com Sat Sep 26 02:45:13 2009 From: vernondcole at gmail.com (Vernon Cole) Date: Fri, 25 Sep 2009 18:45:13 -0600 Subject: [DB-SIG] what is the "correct" way to alter paramstyle in a PEP 249 interface? Message-ID: I am planning to add, as an extension, the ability for adodbapi to change its paramstyle. I personally like "named" much better than "qmark", and it happens that django expects to have "format", so I will add that, too. My question is, what would be an appropriate way to specify the altered paramstyle? 1) As an attribute of the connection: con = adodbapi.connect('spam eggs") con.paramstyle = "named" 2) Make the module global mutable: adodbapi.adodbapi.paramstyle = "named" # [ ick! ] 3) As a named parameter of the connection: con = adodbapi.connect("spam eggs", paramstyle="named") Has anyone else done this? How did they do it? How will some speculated future db-api version 3.0 want it? -- Vernon Cole -------------- next part -------------- An HTML attachment was scrubbed... URL: From mal at egenix.com Sat Sep 26 11:16:01 2009 From: mal at egenix.com (M.-A. Lemburg) Date: Sat, 26 Sep 2009 11:16:01 +0200 Subject: [DB-SIG] what is the "correct" way to alter paramstyle in a PEP 249 interface? In-Reply-To: References: Message-ID: <4ABDDBD1.8090204@egenix.com> Vernon Cole wrote: > I am planning to add, as an extension, the ability for adodbapi to change > its paramstyle. I personally like "named" much better than "qmark", and it > happens that django expects to have "format", so I will add that, too. > > My question is, what would be an appropriate way to specify the altered > paramstyle? > > 1) As an attribute of the connection: > con = adodbapi.connect('spam eggs") > con.paramstyle = "named" Most other configuration parameters are made available on connections and cursors (with the cursor setting overriding the connection one), so I think that's the most DB-API compatible way of implementing this. > 2) Make the module global mutable: > adodbapi.adodbapi.paramstyle = "named" # [ ick! ] > > 3) As a named parameter of the connection: > con = adodbapi.connect("spam eggs", paramstyle="named") > > Has anyone else done this? > How did they do it? > How will some speculated future db-api version 3.0 want it? Probably in the way you mentioned above. The module global would then provide to the default setting. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Sep 26 2009) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ From phd at phd.pp.ru Wed Sep 30 14:39:44 2009 From: phd at phd.pp.ru (Oleg Broytman) Date: Wed, 30 Sep 2009 16:39:44 +0400 Subject: [DB-SIG] SQLObject 0.10.8 Message-ID: <20090930123944.GC9870@phd.pp.ru> Hello! I'm pleased to announce version 0.10.8, a minor bugfix release of 0.10 branch of SQLObject. What is SQLObject ================= SQLObject is an object-relational mapper. Your database tables are described as classes, and rows are instances of those classes. SQLObject is meant to be easy to use and quick to get started with. SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite, Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB). Where is SQLObject ================== Site: http://sqlobject.org Development: http://sqlobject.org/devel/ Mailing list: https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss Archives: http://news.gmane.org/gmane.comp.python.sqlobject Download: http://cheeseshop.python.org/pypi/SQLObject/0.10.8 News and changes: http://sqlobject.org/News.html What's New ========== News since 0.10.7 ----------------- * Fixed a bug in logging to console - convert unicode to str. * Fixed an obscure bug in ConnectionHub triggered by an SQLObject class whose instances can be coerced to boolean False. For a more complete list, please see the news: http://sqlobject.org/News.html Oleg. -- Oleg Broytman http://phd.pp.ru/ phd at phd.pp.ru Programmers don't die, they just GOSUB without RETURN. From phd at phd.pp.ru Wed Sep 30 14:41:20 2009 From: phd at phd.pp.ru (Oleg Broytman) Date: Wed, 30 Sep 2009 16:41:20 +0400 Subject: [DB-SIG] SQLObject 0.11.2 Message-ID: <20090930124120.GG9870@phd.pp.ru> {[xs at OYG]2Q]0#}0sjJp`1^1+B6]A2+{9fW=S