From erik.myllymaki at aviawest.com Tue Apr 3 18:35:07 2007 From: erik.myllymaki at aviawest.com (Erik Myllymaki) Date: Wed Apr 4 02:35:14 2007 Subject: [egenix-users] Transactions in Zope DA In-Reply-To: <429320790703311659u31804c04tba749bfdd65c934a@mail.gmail.com> References: <429320790703311659u31804c04tba749bfdd65c934a@mail.gmail.com> Message-ID: <4612F2BB.1050805@aviawest.com> I am using mxODBC Zope DA 1.0.9 on Windows with Zope Zope 2.9.3, python 2.4.2. I thought that the following zsql method would update and then insert, or do neither(in the case of an error in either the update OR the insert). However, I am seeing data that suggests otherwise. The connection setting "Use Auto-Commit" is NOT enabled. update p_status set to_date = getdate() where strata_lot = and usage = and getdate() between from_date and to_date insert into p_status(strata_lot,usage,employee,status,notes,client_name,shprice,deposit_date,edited_by, from_date, to_date) values( , , , , , , , , , getdate(), '2100-01-01' ) From support at egenix.com Wed Apr 4 13:09:28 2007 From: support at egenix.com (eGenix Support: M.-A. Lemburg) Date: Wed Apr 4 12:09:40 2007 Subject: [egenix-users] Transactions in Zope DA In-Reply-To: <4612F2BB.1050805@aviawest.com> References: <429320790703311659u31804c04tba749bfdd65c934a@mail.gmail.com> <4612F2BB.1050805@aviawest.com> Message-ID: <46137958.4030107@egenix.com> On 2007-04-04 02:35, Erik Myllymaki wrote: > I am using mxODBC Zope DA 1.0.9 on Windows with Zope Zope 2.9.3, python > 2.4.2. > > I thought that the following zsql method would update and then insert, > or do neither(in the case of an error in either the update OR the > insert). However, I am seeing data that suggests otherwise. The two statements get executed on the same connection, so if the second fails, the first should get rolled back as well. > The connection setting "Use Auto-Commit" is NOT enabled. Which database backend and ODBC driver are you using ? It is possible that the database or ODBC does not support transactions in which case, the Zope DA would default to auto-commit even with "Use Auto-Commit" not enabled. > update p_status set > to_date = getdate() > where > strata_lot = > and > usage = > and > getdate() between from_date and to_date > > > > insert into > p_status(strata_lot,usage,employee,status,notes,client_name,shprice,deposit_date,edited_by, > from_date, to_date) > values( > , > , > , > , > , > , > , > , > , getdate(), '2100-01-01' > ) > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 04 2007) >>> 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 mxODBC.Zope.DA for Windows,Linux,Solaris,MacOSX 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 From DEV.K.SEN at saic.com Thu Apr 5 15:28:43 2007 From: DEV.K.SEN at saic.com (Dev Sen) Date: Thu Apr 5 20:28:50 2007 Subject: [egenix-users] Problems with number of results being returned Message-ID: Hi, This is my first post to the list, so I hope my question isn?t too na?ve. I am developing a database app in Zope/Plone using MySQL with the egenix DB adaptor on a Mac Pro. So far everything with the adaptor has been good, although I am now having strange issues. I have some queries which return around 5,000 rows of data. When I run the query with parameters so that only 1200 or so rows are returned there is no problem, however, for larger result sets I get an error saying the connection to the database was lost. Another developer working on the same project (identical code, software versions) but running Windows XP doesn?t have this problem at all. Also, running the queries directly in MySQL works fine. Therefore we think it has something to do with the Mac OSX version of the egenix DB adaptor. Has anyone seen this behavior before? Is this a known bug? Thanks, Dev K Sen Safety and Risk Section Space Technologies Operation, SAIC 350 Broadway, 8th Floor New York, NY 10013 212.431.6905 x252 -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20070405/d12e779e/attachment.htm From charlie at egenix.com Thu Apr 5 23:09:36 2007 From: charlie at egenix.com (Charlie Clark) Date: Thu Apr 5 22:10:04 2007 Subject: [egenix-users] Problems with number of results being returned In-Reply-To: References: Message-ID: Am 05.04.2007, 20:28 Uhr, schrieb Dev Sen : > Hi, > This is my first post to the list, so I hope my question isn?t too na?ve. > I am developing a database app in Zope/Plone using MySQL with the egenix > DB > adaptor on a Mac Pro. So far everything with the adaptor has been good, > although I am now having strange issues. I have some queries which return > around 5,000 rows of data. When I run the query with parameters so that > only > 1200 or so rows are returned there is no problem, however, for larger > result > sets I get an error saying the connection to the database was lost. > Another > developer working on the same project (identical code, software versions) > but running Windows XP doesn?t have this problem at all. Also, running > the > queries directly in MySQL works fine. Therefore we think it has > something to > do with the Mac OSX version of the egenix DB adaptor. > Has anyone seen this behavior before? Is this a known bug? Dev, I believe that MySQL has only just released their ODBC driver for Mac OS X and this is where we suspect the problem is so it's probably a good idea to make sure you have the most uptodate version of this driver. As for limiting the number of rows returned. Are you doing this through the advanced tab in the ZSQL method or through LIMIT in the SQL statement? MySQL (MyASM tables) can be unbelievably slow on certain types of query such as ANSI INNER JOINS or subselects but if you enforce a hard LIMIT in your SQL there should be no reason for a timeout as maybe happening here. Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 mxODBC.Zope.DA for Windows,Linux,Solaris,MacOSX 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 From DEV.K.SEN at saic.com Thu Apr 5 17:26:31 2007 From: DEV.K.SEN at saic.com (Dev Sen) Date: Thu Apr 5 22:26:16 2007 Subject: [egenix-users] Problems with number of results being returned In-Reply-To: Message-ID: Charlie, Thanks for your response. My next line of inquiry was going to be the ODBC adaptor. I am actually using Actual's ODBC driver for Mac so I will try the MySQL one and see if that fixes the issue. I haven't set the limits either in the ZMI or through SQL. On my colleague's Windows machine the 5,000 results sets return very quickly, so timeout isn't an issue. If I find the problem is with the ODBC driver I'll repost to this list just in case anyone else has the same problem in the future. Dev On 4/5/07 4:09 PM, "Charlie Clark" wrote: > Am 05.04.2007, 20:28 Uhr, schrieb Dev Sen : > >> Hi, >> This is my first post to the list, so I hope my question isn?t too na?ve. >> I am developing a database app in Zope/Plone using MySQL with the egenix >> DB >> adaptor on a Mac Pro. So far everything with the adaptor has been good, >> although I am now having strange issues. I have some queries which return >> around 5,000 rows of data. When I run the query with parameters so that >> only >> 1200 or so rows are returned there is no problem, however, for larger >> result >> sets I get an error saying the connection to the database was lost. >> Another >> developer working on the same project (identical code, software versions) >> but running Windows XP doesn?t have this problem at all. Also, running >> the >> queries directly in MySQL works fine. Therefore we think it has >> something to >> do with the Mac OSX version of the egenix DB adaptor. >> Has anyone seen this behavior before? Is this a known bug? > > Dev, > > I believe that MySQL has only just released their ODBC driver for Mac OS X > and this is where we suspect the problem is so it's probably a good idea > to make sure you have the most uptodate version of this driver. As for > limiting the number of rows returned. Are you doing this through the > advanced tab in the ZSQL method or through LIMIT in the SQL statement? > MySQL (MyASM tables) can be unbelievably slow on certain types of query > such as ANSI INNER JOINS or subselects but if you enforce a hard LIMIT in > your SQL there should be no reason for a timeout as maybe happening here. > > Charlie Clark From info at egenix.com Sun Apr 8 16:15:05 2007 From: info at egenix.com (eGenix Team: M.-A. Lemburg) Date: Sun Apr 8 15:27:03 2007 Subject: [egenix-users] ANN: eGenix mx Base and Commercial Distribution 3.0 Release Candidate 2 Message-ID: <4618EAD9.4070601@egenix.com> Hello, we're sorry for keeping you all waiting for so many months, but the 3.0 release has been major piece of work and there have been a number of delays due to external factors and projects which caused us to slip the envisioned release date by two months. In order to not keep you waiting much longer, we've decided to wrap up our release candidate 2 of the eGenix mx Base and Commercial Distribution 3.0 and give you a chance to evaluate the new and enhanced packages. The final GA release is expected to ship in the week of April 16. So, here goes... ________________________________________________________________________ ANNOUNCEMENT eGenix is pleased to announce the immediate availability of the release candidate 2 of our Python extensions distributions eGenix mx Base and eGenix mx Commercial 3.0. ________________________________________________________________________ INTRODUCTION eGenix mx Base and Commercial Distributions are two sets of packages which help you with everyday programming tasks when working with Python. The mx Base distributions contains our open-source offerings: * mxDateTime - date/time types, parsers, tools * mxTextTools - fast text parsing * mxTools - set of new built-ins * mxURL - fast and easy-to-use URL data type * mxUID - unique identifiers * mxStack - fast stack data type with C interface * mxQueue - fast queue data type with C interface * mxProxy - access control and weak reference for Python objects * mxBeeBase - on-disk B+Tree database kit The mx Commercial distribution comes with: * mxODBC, our universal ODBC database interface for Python ________________________________________________________________________ NEWS The 3.0 releases of the eGenix mx Base and mx Commercial distributions contain a huge number of enhancements, bug fixes and additions. Some highlights: * mxTextTools now fully support Unicode, so you can parse Unicode data just as fast as you can 8-bit string data. The package also includes a tag table compiler and new jump target support to simplify working with tag tables. * mxDateTime has support for working with Python's datetime module types, so you can use and combine both if necessary. The parser was enhanced to support even more formats and make it more reliable than ever before. * mxURL and mxUID were previously released as part of our mx Experimental distribution. They have now been integrated into the base distribution, providing easy-to-use data types for common tasks in web programming. * mxODBC has received a large number of enhancements and supports more ODBC drivers than ever. We've worked a lot on the Unicode support and made it more robust, especially on Unix platforms where the ODBC Unicode support has stabilized over the last few years. You can now issue commands using Unicode and exchange Unicode data with the database in various configurable ways. We've also added a few more methods to give you more control of the connections and cursors as well as the .callproc() method that mxODBC 2.0 was missing. Multiple result sets via the .nextset() are also supported, so working with stored procedures should be a lot easier now. Another highlight is the added support for Python's datetime module types and the option to use strings for date/time processing (e.g. to be able to use timezones in timestamps if that's supported by the database). And finally, mxODBC received full 64-bit support, so that you can run mxODBC (and all other mx Extensions) on e.g. AMD64 platforms. * We've switched from the old distutils wininst installer to the new MSI installer for the Windows build. This gives you a lot more options for automatic installs, including unattended installs. See http://www.python.org/download/releases/2.5/msi/ for details. ________________________________________________________________________ UPGRADING Please note that the 2.0 series of the eGenix mx Base and Commercial Distribution do not support Python 2.5 on 64-bit platforms. You are encouraged to upgrade to the new 3.0 series, if you plan to deploy on 64-bit platforms and use Python 2.5 as basis for your applications. ________________________________________________________________________ LICENSES This release brings you all the new features and enhancements that were previously only available in our mxODBC Zope Database Adapter. Like the Zope product, mxODBC now requires that you install a license in order to use it. You can request 30-day evaluation licenses by writing to sales@egenix.com, stating your name (or the name of the company) and the number of eval licenses that you need. We will then issue you licenses and send them to you by email. Please make sure that you can receive ZIP file attachements on the email you specify in the request, since the license files are send out as ZIP attachements. The eGenix mx Base distribution does not require installation of licenses, so you can use straight away. ________________________________________________________________________ DOWNLOADS eGenix mx Base Distribution: * Windows Installer for Python 2.5: http://downloads.egenix.com/python/egenix-mx-base-3.0.0_rc2.win32-py2.5.msi To install, download and then run the installer file. * Linux 32-bit Pre-Built Binary for Python 2.5 UCS4: http://downloads.egenix.com/python/egenix-mx-base-3.0.0_rc2.linux-i686-py2.5_ucs4.prebuilt.zip To install, run "python setup.py build --skip install". * Linux 64-bit Pre-Built Binary for Python 2.5 UCS4: http://downloads.egenix.com/python/egenix-mx-base-3.0.0_rc2.linux-x86_64-py2.5_ucs4.prebuilt.zip To install, run "python setup.py build --skip install". * Source (all other platforms and Python versions): http://downloads.egenix.com/python/egenix-mx-base-3.0.0_rc2.zip To install, run "python setup.py install". eGenix mx Commercial Distribution: * Windows Installer for Python 2.5: http://downloads.egenix.com/python/egenix-mx-commercial-3.0.0_rc2.win32-py2.5.msi To install, download and then run the installer file. * Linux 32-bit Pre-Built Binary for Python 2.5 UCS4: http://downloads.egenix.com/python/egenix-mx-commercial-3.0.0_rc2.linux-i686-py2.5_ucs4.prebuilt.zip To install, run "python setup.py build --skip install". * Linux 64-bit Pre-Built Binary for Python 2.5 UCS4: http://downloads.egenix.com/python/egenix-mx-commercial-3.0.0_rc2.linux-x86_64-py2.5_ucs4.prebuilt.zip To install, run "python setup.py build --skip install". Note that in order to use the eGenix mx Commercial Distribution you need to install the eGenix mx Base Distribution first. Documentation is included in the mx/Doc/ directory of the installation in form of PDF files. This will also be posted on our web-site for easy access. The final release will include downloads for more platforms and combinations of Python version, Unicode version and 32-/64-bit versions. If you have special needs, please let us know. Write to support@egenix.com for information on whether we can support your particular platform. It's likely that we can, given the portability of our code. ________________________________________________________________________ MORE INFORMATION For more information on the eGenix mx Distributions, licensing and download instructions, please write to sales@egenix.com. If you experience problems with the release candidate, we'd appreciate a short description of the problem to support@egenix.com, so that we can fix the problem in the final release. Happy Easter, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 08 2007) >>> 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 mxODBC.Zope.DA for Windows,Linux,Solaris,MacOSX 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 From qwilson1843 at yahoo.com Mon Apr 16 15:27:26 2007 From: qwilson1843 at yahoo.com (Quince Wilson) Date: Mon Apr 16 23:27:31 2007 Subject: [egenix-users] Python 2.5 binaries rpm distribution. Message-ID: <717428.92963.qm@web32703.mail.mud.yahoo.com> Hi, Does anyone have an update on when the rpm distributions for Python 2.5 might be available. Thanks Quince __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From charlie at egenix.com Tue Apr 17 00:31:14 2007 From: charlie at egenix.com (Charlie Clark) Date: Mon Apr 16 23:31:46 2007 Subject: [egenix-users] Python 2.5 binaries rpm distribution. In-Reply-To: <717428.92963.qm@web32703.mail.mud.yahoo.com> References: <717428.92963.qm@web32703.mail.mud.yahoo.com> Message-ID: Am 16.04.2007, 23:27 Uhr, schrieb Quince Wilson : > Hi, > Does anyone have an update on when the rpm > distributions for Python 2.5 might be available. Yes, rpm's will be available when the final product is released which is real soon now. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 mxODBC.Zope.DA for Windows,Linux,Solaris,MacOSX 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 From gregcorradini at gmail.com Wed Apr 18 14:31:29 2007 From: gregcorradini at gmail.com (Greg Corradini) Date: Wed Apr 18 20:31:53 2007 Subject: [egenix-users] Help Understanding mx.ODBC Error Message-ID: <429320790704181131s7c8682c9w1f8b8e8f92a5ea8c@mail.gmail.com> Hello All, A few weeks ago, I wrote two scripts using mx.ODBC on an Access DB. Among other things, both scripts create new tables, performs a query and then inserts the tables with data in a dictionary that I've uploaded from elsewhere. These scripts have run hundreds of times in the last few weeks with no problems. But recently they continue to bail on the *mycursor.execute('An SQL Statement')* after the table has been created. I get the following error message: *Traceback (most recent call last): File "C:\Documents and Settings\marv1shi\Desktop\Workspace\Existence Script\DBF Checker\Access_SQL.py", line 35, in ? curse.execute(sql) ProgrammingError: ('07001', -3010, '[Microsoft][ODBC Microsoft Access Driver] Too few parameters. Expected 4.', 4612)* ** The real stinker, however, is that after it bails I can manually call * mycursor.execute('An SQL Statement')*, then call my insert statement* *in the Python Shell and it works fine. I just can't figure out how to reconcile this problem. Has anybody run into this before? Thanks Greg Corradini -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20070418/6b68802c/attachment.htm From mal at egenix.com Wed Apr 18 23:04:40 2007 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Apr 18 22:04:45 2007 Subject: [egenix-users] Help Understanding mx.ODBC Error In-Reply-To: <429320790704181131s7c8682c9w1f8b8e8f92a5ea8c@mail.gmail.com> References: <429320790704181131s7c8682c9w1f8b8e8f92a5ea8c@mail.gmail.com> Message-ID: <462679D8.3050706@egenix.com> On 2007-04-18 20:31, Greg Corradini wrote: > Hello All, > A few weeks ago, I wrote two scripts using mx.ODBC on an Access DB. Among > other things, both scripts create new tables, performs a query and then > inserts the tables with data in a dictionary that I've uploaded from > elsewhere. These scripts have run hundreds of times in the last few weeks > with no problems. > > But recently they continue to bail on the *mycursor.execute('An SQL > Statement')* after the table has been created. I get the following error > message: > *Traceback (most recent call last): > File "C:\Documents and Settings\marv1shi\Desktop\Workspace\Existence > Script\DBF Checker\Access_SQL.py", line 35, in ? > curse.execute(sql) > ProgrammingError: ('07001', -3010, '[Microsoft][ODBC Microsoft Access > Driver] Too few parameters. Expected 4.', 4612)* > ** > The real stinker, however, is that after it bails I can manually call * > mycursor.execute('An SQL Statement')*, then call my insert statement* *in > the Python Shell and it works fine. > > I just can't figure out how to reconcile this problem. Has anybody run into > this before? No, but then these things often depend on the version of the ODBC driver you're using. Could you provide the SQL in question ? Ie. the statement that leads to the error ? Also, you should try to turn of connection pooling in the MS ODBC manager and see whether that makes a difference - could be that the two scripts both get shared connections that haven't been fully reset and then disturb each other. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 18 2007) >>> 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 mxODBC.Zope.DA for Windows,Linux,Solaris,MacOSX 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 From sudesh.soni at ebusinessware.com Mon Apr 23 16:23:48 2007 From: sudesh.soni at ebusinessware.com (Sudesh soni) Date: Mon Apr 23 22:27:02 2007 Subject: [egenix-users] Operational error Message-ID: <012901c785dc$ebf379d0$0264000a@FINTSUDESH> Hi, I would appreciate if anyone can help me out to resolve the following error: "Operational Error " due to timeout. How can I fix that? Regards Suson-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20070423/ad01d2d4/attachment.htm From charlie at egenix.com Tue Apr 24 00:03:04 2007 From: charlie at egenix.com (Charlie Clark) Date: Mon Apr 23 23:03:14 2007 Subject: [egenix-users] Operational error In-Reply-To: <012901c785dc$ebf379d0$0264000a@FINTSUDESH> References: <012901c785dc$ebf379d0$0264000a@FINTSUDESH> Message-ID: Am 23.04.2007, 21:23 Uhr, schrieb Sudesh soni : > Hi, > I would appreciate if anyone can help me out to resolve the following > error: > "Operational Error " > due to timeout. > How can I fix that? If the connection to the database has timed out you should look at your database and networks environments as the error is unrelated to Python or mxODBC. In order for anyone to be able to help you please provide full details and particularly the complete error message. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 mxODBC.Zope.DA for Windows,Linux,Solaris,MacOSX 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 From mal at egenix.com Fri Apr 27 19:28:48 2007 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Apr 27 18:28:54 2007 Subject: [egenix-users] ANN: eGenix mx Base and Commercial Distribution 3.0 Release Candidate 2 In-Reply-To: <4618EAD9.4070601@egenix.com> References: <4618EAD9.4070601@egenix.com> Message-ID: <463224C0.50005@egenix.com> Hello, just to keep you updated: we are still working on the release and will also launch a new web-site right along with it. Especially the new web-site is currently keeping us very busy and is also taking longer than expected. OTOH, it will look a lot nicer than the current one :-) There won't be many changes between the release candidate and the final version, with one exception: we've decided to rename the "eGenix mx Commercial" distribution into "eGenix mxODBC" distribution. Not much of a change, but hopefully makes things a little more straight forward. The links below are still valid and accessible, so please give the release candidate a try. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2007) >>> 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 mxODBC.Zope.DA for Windows,Linux,Solaris,MacOSX 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 On 2007-04-08 15:15, eGenix Team: M.-A. Lemburg wrote: > Hello, > > we're sorry for keeping you all waiting for so many months, but the 3.0 > release has been major piece of work and there have been a number of > delays due to external factors and projects which caused us to slip > the envisioned release date by two months. > > In order to not keep you waiting much longer, we've decided to wrap up > our release candidate 2 of the eGenix mx Base and Commercial Distribution 3.0 > and give you a chance to evaluate the new and enhanced packages. > > The final GA release is expected to ship in the week of April 16. > > So, here goes... > > ________________________________________________________________________ > ANNOUNCEMENT > > eGenix is pleased to announce the immediate availability of the > release candidate 2 of our Python extensions distributions > eGenix mx Base and eGenix mx Commercial 3.0. > > ________________________________________________________________________ > INTRODUCTION > > eGenix mx Base and Commercial Distributions are two sets of packages > which help you with everyday programming tasks when working with Python. > > The mx Base distributions contains our open-source offerings: > > * mxDateTime - date/time types, parsers, tools > * mxTextTools - fast text parsing > * mxTools - set of new built-ins > * mxURL - fast and easy-to-use URL data type > * mxUID - unique identifiers > * mxStack - fast stack data type with C interface > * mxQueue - fast queue data type with C interface > * mxProxy - access control and weak reference for Python objects > * mxBeeBase - on-disk B+Tree database kit > > The mx Commercial distribution comes with: > > * mxODBC, our universal ODBC database interface for Python > > ________________________________________________________________________ > NEWS > > The 3.0 releases of the eGenix mx Base and mx Commercial distributions > contain a huge number of enhancements, bug fixes and additions. > > Some highlights: > > * mxTextTools now fully support Unicode, so you can parse Unicode > data just as fast as you can 8-bit string data. > > The package also includes a tag table compiler and new jump > target support to simplify working with tag tables. > > * mxDateTime has support for working with Python's datetime module > types, so you can use and combine both if necessary. > > The parser was enhanced to support even more formats and make > it more reliable than ever before. > > * mxURL and mxUID were previously released as part of our mx > Experimental distribution. > > They have now been integrated into the base distribution, providing > easy-to-use data types for common tasks in web programming. > > * mxODBC has received a large number of enhancements and supports > more ODBC drivers than ever. > > We've worked a lot on the Unicode support and made it more robust, > especially on Unix platforms where the ODBC Unicode support has > stabilized over the last few years. You can now issue commands > using Unicode and exchange Unicode data with the database in > various configurable ways. > > We've also added a few more methods to give you more control of > the connections and cursors as well as the .callproc() method > that mxODBC 2.0 was missing. > > Multiple result sets via the .nextset() are also supported, so > working with stored procedures should be a lot easier now. > > Another highlight is the added support for Python's datetime > module types and the option to use strings for date/time > processing (e.g. to be able to use timezones in timestamps > if that's supported by the database). > > And finally, mxODBC received full 64-bit support, so that you > can run mxODBC (and all other mx Extensions) on e.g. AMD64 > platforms. > > * We've switched from the old distutils wininst installer to the > new MSI installer for the Windows build. This gives you a lot > more options for automatic installs, including unattended > installs. See http://www.python.org/download/releases/2.5/msi/ > for details. > > ________________________________________________________________________ > UPGRADING > > Please note that the 2.0 series of the eGenix mx Base and Commercial > Distribution do not support Python 2.5 on 64-bit platforms. > > You are encouraged to upgrade to the new 3.0 series, if you plan to > deploy on 64-bit platforms and use Python 2.5 as basis for your > applications. > > ________________________________________________________________________ > LICENSES > > This release brings you all the new features and enhancements that > were previously only available in our mxODBC Zope Database Adapter. > > Like the Zope product, mxODBC now requires that you install a license > in order to use it. > > You can request 30-day evaluation licenses by writing to sales@egenix.com, > stating your name (or the name of the company) and the number of eval > licenses that you need. We will then issue you licenses and send > them to you by email. Please make sure that you can receive ZIP > file attachements on the email you specify in the request, since the > license files are send out as ZIP attachements. > > The eGenix mx Base distribution does not require installation of > licenses, so you can use straight away. > > ________________________________________________________________________ > DOWNLOADS > > eGenix mx Base Distribution: > > * Windows Installer for Python 2.5: > > http://downloads.egenix.com/python/egenix-mx-base-3.0.0_rc2.win32-py2.5.msi > > To install, download and then run the installer file. > > * Linux 32-bit Pre-Built Binary for Python 2.5 UCS4: > > http://downloads.egenix.com/python/egenix-mx-base-3.0.0_rc2.linux-i686-py2.5_ucs4.prebuilt.zip > > To install, run "python setup.py build --skip install". > > * Linux 64-bit Pre-Built Binary for Python 2.5 UCS4: > > http://downloads.egenix.com/python/egenix-mx-base-3.0.0_rc2.linux-x86_64-py2.5_ucs4.prebuilt.zip > > To install, run "python setup.py build --skip install". > > * Source (all other platforms and Python versions): > > http://downloads.egenix.com/python/egenix-mx-base-3.0.0_rc2.zip > > To install, run "python setup.py install". > > eGenix mx Commercial Distribution: > > * Windows Installer for Python 2.5: > > http://downloads.egenix.com/python/egenix-mx-commercial-3.0.0_rc2.win32-py2.5.msi > > To install, download and then run the installer file. > > * Linux 32-bit Pre-Built Binary for Python 2.5 UCS4: > > http://downloads.egenix.com/python/egenix-mx-commercial-3.0.0_rc2.linux-i686-py2.5_ucs4.prebuilt.zip > > To install, run "python setup.py build --skip install". > > * Linux 64-bit Pre-Built Binary for Python 2.5 UCS4: > > http://downloads.egenix.com/python/egenix-mx-commercial-3.0.0_rc2.linux-x86_64-py2.5_ucs4.prebuilt.zip > > To install, run "python setup.py build --skip install". > > Note that in order to use the eGenix mx Commercial Distribution > you need to install the eGenix mx Base Distribution first. > > Documentation is included in the mx/Doc/ directory of the installation > in form of PDF files. This will also be posted on our web-site for > easy access. > > The final release will include downloads for more platforms and combinations > of Python version, Unicode version and 32-/64-bit versions. > > If you have special needs, please let us know. Write to support@egenix.com > for information on whether we can support your particular platform. It's > likely that we can, given the portability of our code. > > ________________________________________________________________________ > MORE INFORMATION > > For more information on the eGenix mx Distributions, licensing > and download instructions, please write to sales@egenix.com. > > If you experience problems with the release candidate, we'd appreciate > a short description of the problem to support@egenix.com, so that > we can fix the problem in the final release. > > > Happy Easter,