From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 11:13:18 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 13 11:13:18 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 13 11:13:18 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 13 11:13:18 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 11:13:18 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Jan 13 11:13:18 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Fri Jan 13 11:13:18 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Jan 13 11:13:18 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:13:51 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 13 15:13:51 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 13 15:13:51 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 13 15:13:51 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:13:51 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Jan 13 15:13:51 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Fri Jan 13 15:13:51 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Jan 13 15:13:51 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:21:13 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 13 15:21:13 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 13 15:21:13 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 13 15:21:13 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:21:13 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Jan 13 15:21:13 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Fri Jan 13 15:21:13 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Jan 13 15:21:13 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 16:00:45 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 13 16:00:45 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 13 16:00:45 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 13 16:00:45 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 16:00:45 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Jan 13 16:00:45 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Fri Jan 13 16:00:45 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Jan 13 16:00:46 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 20:01:34 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 13 20:01:34 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 13 20:01:34 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 13 20:01:34 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 20:01:34 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Jan 13 20:01:34 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Fri Jan 13 20:01:34 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Jan 13 20:01:34 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 08:02:13 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 14 08:02:14 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 14 08:02:14 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 14 08:02:14 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 08:02:14 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Jan 14 08:02:14 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sat Jan 14 08:02:14 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Jan 14 08:02:14 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 12:00:42 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 14 12:00:43 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 14 12:00:43 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 14 12:00:43 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 12:00:43 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Jan 14 12:00:43 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sat Jan 14 12:00:43 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Jan 14 12:00:43 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 16:00:42 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 14 16:00:42 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 14 16:00:42 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 14 16:00:42 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 16:00:42 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Jan 14 16:00:42 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sat Jan 14 16:00:42 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Jan 14 16:00:42 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 20:00:39 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 14 20:00:39 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 14 20:00:39 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 14 20:00:39 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 20:00:39 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Jan 14 20:00:39 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sat Jan 14 20:00:39 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Jan 14 20:00:39 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 08:02:04 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 15 08:02:04 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 15 08:02:04 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 15 08:02:04 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 08:02:04 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Jan 15 08:02:04 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sun Jan 15 08:02:04 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Jan 15 08:02:04 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 12:00:48 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 15 12:00:48 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 15 12:00:48 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 15 12:00:48 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 12:00:49 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Jan 15 12:00:49 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sun Jan 15 12:00:49 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Jan 15 12:00:49 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 16:00:41 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 15 16:00:42 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 15 16:00:42 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 15 16:00:42 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 16:00:42 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Jan 15 16:00:42 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sun Jan 15 16:00:42 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Jan 15 16:00:42 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 20:00:38 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 15 20:00:38 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 15 20:00:38 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 15 20:00:38 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 20:00:38 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Jan 15 20:00:38 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sun Jan 15 20:00:38 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Jan 15 20:00:38 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 08:02:27 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 16 08:02:27 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 16 08:02:27 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 16 08:02:27 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 08:02:27 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Jan 16 08:02:27 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Mon Jan 16 08:02:27 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Jan 16 08:02:27 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 12:00:46 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 16 12:00:46 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 16 12:00:46 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 16 12:00:46 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 12:00:46 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Jan 16 12:00:46 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Mon Jan 16 12:00:46 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Jan 16 12:00:46 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 16:00:46 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 16 16:00:46 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 16 16:00:46 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 16 16:00:46 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 16:00:46 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Jan 16 16:00:46 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Mon Jan 16 16:00:46 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Jan 16 16:00:46 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 20:00:40 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 16 20:00:40 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 16 20:00:40 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 16 20:00:40 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 20:00:40 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Jan 16 20:00:40 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Mon Jan 16 20:00:40 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Jan 16 20:00:40 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 08:02:29 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 17 08:02:29 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 17 08:02:29 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 17 08:02:29 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 08:02:29 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Jan 17 08:02:29 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Tue Jan 17 08:02:29 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Jan 17 08:02:29 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 12:00:55 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 17 12:00:55 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 17 12:00:55 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 17 12:00:55 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 12:00:55 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Jan 17 12:00:55 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Tue Jan 17 12:00:55 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Jan 17 12:00:55 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 16:00:46 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 17 16:00:47 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 17 16:00:47 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 17 16:00:47 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 16:00:47 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Jan 17 16:00:47 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Tue Jan 17 16:00:47 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Jan 17 16:00:47 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 20:00:48 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 17 20:00:49 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 17 20:00:49 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 17 20:00:49 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 20:00:49 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Jan 17 20:00:49 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Tue Jan 17 20:00:49 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Jan 17 20:00:49 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 08:04:11 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Jan 18 08:04:11 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Jan 18 08:04:11 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Jan 18 08:04:11 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 08:04:11 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Jan 18 08:04:11 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Wed Jan 18 08:04:11 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Jan 18 08:04:11 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 12:00:59 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Jan 18 12:00:59 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Jan 18 12:00:59 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Jan 18 12:00:59 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 12:00:59 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Jan 18 12:00:59 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Wed Jan 18 12:00:59 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Jan 18 12:00:59 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 16:01:23 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Jan 18 16:01:23 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Jan 18 16:01:23 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Jan 18 16:01:23 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 16:01:23 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Jan 18 16:01:23 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Wed Jan 18 16:01:23 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Jan 18 16:01:23 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 20:00:48 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Jan 18 20:00:49 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Jan 18 20:00:49 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Jan 18 20:00:49 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 20:00:49 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Jan 18 20:00:49 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Wed Jan 18 20:00:49 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Jan 18 20:00:49 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 08:04:33 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Jan 19 08:04:33 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Jan 19 08:04:33 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Jan 19 08:04:33 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 08:04:33 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Jan 19 08:04:33 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Thu Jan 19 08:04:33 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Jan 19 08:04:33 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 12:00:57 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Jan 19 12:00:57 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Jan 19 12:00:57 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Jan 19 12:00:57 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 12:00:57 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Jan 19 12:00:57 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Thu Jan 19 12:00:57 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Jan 19 12:00:57 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 16:02:43 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Jan 19 16:02:44 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Jan 19 16:02:44 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Jan 19 16:02:44 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 16:02:44 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Jan 19 16:02:44 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Thu Jan 19 16:02:44 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Jan 19 16:02:44 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 20:00:44 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Jan 19 20:00:44 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Jan 19 20:00:44 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Jan 19 20:00:44 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 20:00:44 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Jan 19 20:00:45 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Thu Jan 19 20:00:45 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Jan 19 20:00:45 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 08:06:31 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 20 08:06:32 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 20 08:06:32 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 20 08:06:32 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 08:06:32 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Jan 20 08:06:32 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Fri Jan 20 08:06:32 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Jan 20 08:06:32 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 12:01:55 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 20 12:01:55 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 20 12:01:55 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 20 12:01:56 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 12:01:56 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Jan 20 12:01:56 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Fri Jan 20 12:01:56 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Jan 20 12:01:56 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 16:00:49 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 20 16:00:49 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 20 16:00:49 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 20 16:00:49 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 16:00:49 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Jan 20 16:00:49 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Fri Jan 20 16:00:49 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Jan 20 16:00:49 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 20:00:44 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 20 20:00:44 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 20 20:00:44 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 20 20:00:44 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 20:00:44 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Jan 20 20:00:44 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Fri Jan 20 20:00:44 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Jan 20 20:00:44 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 08:03:47 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 21 08:03:47 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 21 08:03:47 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 21 08:03:47 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 08:03:47 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Jan 21 08:03:47 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sat Jan 21 08:03:47 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Jan 21 08:03:47 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 12:00:58 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 21 12:00:59 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 21 12:00:59 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 21 12:00:59 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 12:00:59 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Jan 21 12:00:59 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sat Jan 21 12:00:59 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Jan 21 12:00:59 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 16:00:48 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 21 16:00:48 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 21 16:00:48 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 21 16:00:48 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 16:00:48 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Jan 21 16:00:48 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sat Jan 21 16:00:48 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Jan 21 16:00:48 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 20:00:47 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 21 20:00:47 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 21 20:00:47 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 21 20:00:47 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 20:00:47 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Jan 21 20:00:47 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sat Jan 21 20:00:47 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Jan 21 20:00:47 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 08:02:40 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 22 08:02:40 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 22 08:02:40 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 22 08:02:40 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 08:02:40 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Jan 22 08:02:40 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sun Jan 22 08:02:40 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Jan 22 08:02:40 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 12:00:48 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 22 12:00:48 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 22 12:00:48 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 22 12:00:48 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 12:00:48 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Jan 22 12:00:48 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sun Jan 22 12:00:48 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Jan 22 12:00:48 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 16:01:13 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 22 16:01:13 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 22 16:01:13 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 22 16:01:13 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 16:01:13 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Jan 22 16:01:13 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sun Jan 22 16:01:13 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Jan 22 16:01:13 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 20:01:10 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 22 20:01:10 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 22 20:01:10 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 22 20:01:10 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 20:01:10 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Jan 22 20:01:10 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sun Jan 22 20:01:10 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Jan 22 20:01:10 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 08:02:31 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 23 08:02:32 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 23 08:02:32 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 23 08:02:32 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 08:02:32 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Jan 23 08:02:32 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Mon Jan 23 08:02:32 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Jan 23 08:02:32 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 12:00:53 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 23 12:00:53 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 23 12:00:53 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 23 12:00:53 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 12:00:53 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Jan 23 12:00:53 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Mon Jan 23 12:00:53 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Jan 23 12:00:53 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 16:01:39 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 23 16:01:39 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 23 16:01:39 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 23 16:01:39 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 16:01:39 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Jan 23 16:01:39 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Mon Jan 23 16:01:39 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Jan 23 16:01:39 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 20:00:49 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 23 20:00:50 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 23 20:00:50 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 23 20:00:50 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 20:00:50 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Jan 23 20:00:50 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Mon Jan 23 20:00:50 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Jan 23 20:00:50 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 08:03:03 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 24 08:03:04 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 24 08:03:04 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 24 08:03:04 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 08:03:04 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Jan 24 08:03:04 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Tue Jan 24 08:03:04 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Jan 24 08:03:04 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 12:02:41 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 24 12:02:42 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 24 12:02:43 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 24 12:02:43 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 12:02:43 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Jan 24 12:02:43 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Tue Jan 24 12:02:43 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Jan 24 12:02:43 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 16:01:16 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 24 16:01:16 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 24 16:01:16 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 24 16:01:16 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 16:01:16 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Jan 24 16:01:16 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Tue Jan 24 16:01:17 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Jan 24 16:01:17 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 20:01:48 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 24 20:01:48 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 24 20:01:48 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 24 20:01:48 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 20:01:48 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Jan 24 20:01:48 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Tue Jan 24 20:01:48 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Jan 24 20:01:48 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 08:01:58 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Jan 25 08:01:58 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Jan 25 08:01:58 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Jan 25 08:01:58 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 08:01:58 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Jan 25 08:01:58 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Wed Jan 25 08:01:58 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Jan 25 08:01:58 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 12:00:59 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Jan 25 12:00:59 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Jan 25 12:00:59 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Jan 25 12:00:59 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 12:00:59 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Jan 25 12:00:59 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Wed Jan 25 12:00:59 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Jan 25 12:00:59 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 16:00:57 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Jan 25 16:00:57 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Jan 25 16:00:57 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Jan 25 16:00:57 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 16:00:57 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Jan 25 16:00:57 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Wed Jan 25 16:00:57 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Jan 25 16:00:57 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 20:00:51 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Jan 25 20:00:51 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Jan 25 20:00:51 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Jan 25 20:00:51 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 20:00:51 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Jan 25 20:00:51 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Wed Jan 25 20:00:51 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Jan 25 20:00:51 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 08:05:25 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Jan 26 08:05:25 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Jan 26 08:05:25 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Jan 26 08:05:26 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 08:05:26 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Jan 26 08:05:26 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Thu Jan 26 08:05:26 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Jan 26 08:05:26 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 12:01:01 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Jan 26 12:01:03 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Jan 26 12:01:03 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Jan 26 12:01:03 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 12:01:03 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Jan 26 12:01:03 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Thu Jan 26 12:01:03 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Jan 26 12:01:03 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 16:00:50 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Jan 26 16:00:50 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Jan 26 16:00:50 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Jan 26 16:00:50 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 16:00:50 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Jan 26 16:00:50 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Thu Jan 26 16:00:50 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Jan 26 16:00:50 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 20:00:44 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Jan 26 20:00:45 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Jan 26 20:00:45 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Jan 26 20:00:45 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 20:00:45 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Jan 26 20:00:45 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Thu Jan 26 20:00:45 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Jan 26 20:00:45 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 08:06:22 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 27 08:06:23 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 27 08:06:23 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 27 08:06:23 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 08:06:23 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Jan 27 08:06:23 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Fri Jan 27 08:06:23 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Jan 27 08:06:23 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 12:02:05 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 27 12:02:05 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 27 12:02:05 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 27 12:02:05 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 12:02:05 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Jan 27 12:02:05 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Fri Jan 27 12:02:05 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Jan 27 12:02:05 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 16:01:01 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 27 16:01:01 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 27 16:01:01 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 27 16:01:01 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 16:01:01 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Jan 27 16:01:01 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Fri Jan 27 16:01:01 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Jan 27 16:01:01 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 20:00:52 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 27 20:00:52 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 27 20:00:52 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Jan 27 20:00:52 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 20:00:52 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Jan 27 20:00:52 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Fri Jan 27 20:00:52 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Jan 27 20:00:52 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 08:05:27 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 28 08:05:27 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 28 08:05:27 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 28 08:05:27 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 08:05:27 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Jan 28 08:05:27 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sat Jan 28 08:05:27 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Jan 28 08:05:27 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 12:01:52 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 28 12:01:52 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 28 12:01:52 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 28 12:01:52 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 12:01:52 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Jan 28 12:01:52 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sat Jan 28 12:01:52 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Jan 28 12:01:52 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 16:00:51 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 28 16:00:51 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 28 16:00:51 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 28 16:00:51 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 16:00:51 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Jan 28 16:00:51 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sat Jan 28 16:00:51 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Jan 28 16:00:51 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 20:00:51 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 28 20:00:51 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 28 20:00:51 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Jan 28 20:00:51 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 20:00:51 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Jan 28 20:00:51 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sat Jan 28 20:00:51 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Jan 28 20:00:51 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 08:07:19 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 29 08:07:20 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 29 08:07:20 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 29 08:07:20 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 08:07:20 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Jan 29 08:07:20 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sun Jan 29 08:07:21 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Jan 29 08:07:21 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 12:00:57 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 29 12:00:58 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 29 12:00:58 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 29 12:00:58 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 12:00:58 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Jan 29 12:00:58 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sun Jan 29 12:00:58 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Jan 29 12:00:58 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 16:00:51 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 29 16:00:51 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 29 16:00:51 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 29 16:00:51 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 16:00:51 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Jan 29 16:00:51 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sun Jan 29 16:00:51 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Jan 29 16:00:51 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 20:00:52 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 29 20:00:52 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 29 20:00:52 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Jan 29 20:00:52 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 20:00:52 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Jan 29 20:00:52 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sun Jan 29 20:00:52 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Jan 29 20:00:52 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 08:08:08 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 30 08:08:10 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 30 08:08:10 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 30 08:08:10 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 08:08:10 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Jan 30 08:08:10 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Mon Jan 30 08:08:10 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Jan 30 08:08:10 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 12:03:47 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 30 12:03:47 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 30 12:03:47 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 30 12:03:47 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 12:03:47 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Jan 30 12:03:47 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Mon Jan 30 12:03:47 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Jan 30 12:03:47 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 16:04:00 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 30 16:04:01 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 30 16:04:01 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 30 16:04:01 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 16:04:01 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Jan 30 16:04:01 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Mon Jan 30 16:04:01 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Jan 30 16:04:01 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 20:02:06 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 30 20:02:07 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 30 20:02:07 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Jan 30 20:02:07 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 20:02:07 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Jan 30 20:02:07 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Mon Jan 30 20:02:07 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Jan 30 20:02:07 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 08:07:39 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 31 08:07:39 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 31 08:07:39 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 31 08:07:39 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 08:07:39 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Jan 31 08:07:39 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Tue Jan 31 08:07:39 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Jan 31 08:07:39 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 12:04:08 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 31 12:04:08 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 31 12:04:08 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 31 12:04:08 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 12:04:08 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Jan 31 12:04:08 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Tue Jan 31 12:04:08 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Jan 31 12:04:08 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 16:02:10 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 31 16:02:11 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 31 16:02:11 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 31 16:02:11 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 16:02:11 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Jan 31 16:02:11 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Tue Jan 31 16:02:11 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Jan 31 16:02:11 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 20:01:02 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 31 20:01:02 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 31 20:01:02 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Jan 31 20:01:02 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 20:01:03 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Jan 31 20:01:03 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Tue Jan 31 20:01:03 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Jan 31 20:01:03 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 08:09:22 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 1 08:09:22 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 1 08:09:22 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 1 08:09:22 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 08:09:22 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Feb 1 08:09:22 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Wed Feb 1 08:09:22 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Feb 1 08:09:22 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 12:02:36 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 1 12:02:37 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 1 12:02:37 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 1 12:02:37 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 12:02:37 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Feb 1 12:02:37 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Wed Feb 1 12:02:37 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Feb 1 12:02:37 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 16:00:58 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 1 16:00:58 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 1 16:00:58 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 1 16:00:58 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 16:00:58 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Feb 1 16:00:58 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Wed Feb 1 16:00:58 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Feb 1 16:00:58 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 20:00:58 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 1 20:00:58 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 1 20:00:58 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 1 20:00:58 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 20:00:58 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Feb 1 20:00:58 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Wed Feb 1 20:00:58 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Feb 1 20:00:58 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 08:11:49 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 2 08:11:49 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 2 08:11:49 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 2 08:11:49 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 08:11:49 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Feb 2 08:11:49 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Thu Feb 2 08:11:49 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Feb 2 08:11:49 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 12:02:41 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 2 12:02:41 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 2 12:02:41 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 2 12:02:41 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 12:02:41 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Feb 2 12:02:41 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Thu Feb 2 12:02:41 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Feb 2 12:02:41 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 16:01:06 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 2 16:01:07 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 2 16:01:07 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 2 16:01:07 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 16:01:07 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Feb 2 16:01:07 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Thu Feb 2 16:01:07 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Feb 2 16:01:07 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 20:00:57 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 2 20:00:57 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 2 20:00:57 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 2 20:00:57 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 20:00:57 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Feb 2 20:00:57 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Thu Feb 2 20:00:57 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Feb 2 20:00:57 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 08:11:32 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Feb 3 08:11:33 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Feb 3 08:11:33 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Feb 3 08:11:33 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 08:11:34 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Feb 3 08:11:34 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Fri Feb 3 08:11:34 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Feb 3 08:11:34 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 12:02:31 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Feb 3 12:02:31 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Feb 3 12:02:31 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Feb 3 12:02:31 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 12:02:31 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Feb 3 12:02:31 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Fri Feb 3 12:02:31 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Feb 3 12:02:31 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 16:00:54 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Feb 3 16:00:54 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Feb 3 16:00:55 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Feb 3 16:00:55 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 16:00:55 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Feb 3 16:00:55 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Fri Feb 3 16:00:55 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Feb 3 16:00:55 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 20:00:59 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Feb 3 20:00:59 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Feb 3 20:01:00 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Feb 3 20:01:00 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 20:01:00 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Feb 3 20:01:00 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Fri Feb 3 20:01:00 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Feb 3 20:01:01 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 08:07:20 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Feb 4 08:07:21 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Feb 4 08:07:22 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Feb 4 08:07:22 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 08:07:22 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Feb 4 08:07:22 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sat Feb 4 08:07:22 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Feb 4 08:07:22 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 12:02:35 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Feb 4 12:02:35 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Feb 4 12:02:35 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Feb 4 12:02:35 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 12:02:35 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Feb 4 12:02:35 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sat Feb 4 12:02:35 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Feb 4 12:02:35 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 16:01:09 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Feb 4 16:01:09 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Feb 4 16:01:09 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Feb 4 16:01:09 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 16:01:09 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Feb 4 16:01:09 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sat Feb 4 16:01:09 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Feb 4 16:01:09 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 20:01:00 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Feb 4 20:01:00 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Feb 4 20:01:00 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Feb 4 20:01:00 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 20:01:00 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Feb 4 20:01:00 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sat Feb 4 20:01:00 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Feb 4 20:01:00 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 08:07:37 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Feb 5 08:07:38 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Feb 5 08:07:38 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Feb 5 08:07:38 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 08:07:38 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Feb 5 08:07:38 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sun Feb 5 08:07:38 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Feb 5 08:07:38 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 12:02:35 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Feb 5 12:02:36 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Feb 5 12:02:36 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Feb 5 12:02:36 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 12:02:36 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Feb 5 12:02:36 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sun Feb 5 12:02:36 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Feb 5 12:02:36 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 16:01:04 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Feb 5 16:01:04 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Feb 5 16:01:04 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Feb 5 16:01:04 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 16:01:04 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Feb 5 16:01:04 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sun Feb 5 16:01:04 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Feb 5 16:01:04 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 20:00:57 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Feb 5 20:00:57 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Feb 5 20:00:57 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Feb 5 20:00:57 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 20:00:57 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Feb 5 20:00:57 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sun Feb 5 20:00:57 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Feb 5 20:00:57 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 08:13:37 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Feb 6 08:13:40 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Feb 6 08:13:40 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Feb 6 08:13:40 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 08:13:40 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Feb 6 08:13:40 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Mon Feb 6 08:13:40 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Feb 6 08:13:40 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 12:02:34 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Feb 6 12:02:34 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Feb 6 12:02:34 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Feb 6 12:02:34 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 12:02:34 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Feb 6 12:02:34 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Mon Feb 6 12:02:34 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Feb 6 12:02:34 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 16:01:02 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Feb 6 16:01:03 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Feb 6 16:01:03 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Feb 6 16:01:03 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 16:01:03 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Feb 6 16:01:03 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Mon Feb 6 16:01:03 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Feb 6 16:01:03 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 20:00:58 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Feb 6 20:00:58 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Feb 6 20:00:58 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Feb 6 20:00:58 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 20:00:58 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Feb 6 20:00:58 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Mon Feb 6 20:00:58 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Feb 6 20:00:58 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 08:21:16 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Feb 7 08:21:18 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Feb 7 08:21:18 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Feb 7 08:21:18 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 08:21:18 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Feb 7 08:21:19 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Tue Feb 7 08:21:19 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Feb 7 08:21:19 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 12:03:08 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Feb 7 12:03:10 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Feb 7 12:03:10 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Feb 7 12:03:10 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 12:03:10 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Feb 7 12:03:10 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Tue Feb 7 12:03:10 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Feb 7 12:03:10 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 16:01:06 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Feb 7 16:01:06 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Feb 7 16:01:06 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Feb 7 16:01:06 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 16:01:06 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Feb 7 16:01:06 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Tue Feb 7 16:01:06 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Feb 7 16:01:06 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 20:01:01 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Feb 7 20:01:01 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Feb 7 20:01:01 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Feb 7 20:01:01 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 20:01:01 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Feb 7 20:01:01 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Tue Feb 7 20:01:01 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Feb 7 20:01:01 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 08:21:09 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 8 08:21:11 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 8 08:21:11 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 8 08:21:11 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 08:21:11 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Feb 8 08:21:11 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Wed Feb 8 08:21:13 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Feb 8 08:21:13 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 12:03:02 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 8 12:03:04 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 8 12:03:04 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 8 12:03:04 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 12:03:04 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Feb 8 12:03:04 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Wed Feb 8 12:03:04 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Feb 8 12:03:04 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 16:01:10 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 8 16:01:10 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 8 16:01:10 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 8 16:01:10 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 16:01:10 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Feb 8 16:01:10 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Wed Feb 8 16:01:10 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Feb 8 16:01:10 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 20:00:59 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 8 20:00:59 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 8 20:00:59 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 8 20:00:59 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 20:00:59 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Feb 8 20:00:59 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Wed Feb 8 20:00:59 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Feb 8 20:00:59 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 08:08:40 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 9 08:08:41 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 9 08:08:42 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 9 08:08:42 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 08:08:42 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Feb 9 08:08:42 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Thu Feb 9 08:08:42 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Feb 9 08:08:42 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 12:02:50 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 9 12:02:50 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 9 12:02:50 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 9 12:02:50 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 12:02:50 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Feb 9 12:02:50 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Thu Feb 9 12:02:50 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Feb 9 12:02:51 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 16:01:11 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 9 16:01:11 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 9 16:01:11 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 9 16:01:11 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 16:01:11 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Feb 9 16:01:11 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Thu Feb 9 16:01:11 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Feb 9 16:01:11 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 20:01:05 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 9 20:01:05 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 9 20:01:05 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 9 20:01:05 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 20:01:05 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Feb 9 20:01:05 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Thu Feb 9 20:01:05 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Feb 9 20:01:05 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 08:18:13 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Feb 10 08:18:22 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Feb 10 08:18:22 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Feb 10 08:18:22 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 08:18:22 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Feb 10 08:18:22 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Fri Feb 10 08:18:22 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Feb 10 08:18:22 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 12:03:28 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Feb 10 12:03:28 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Feb 10 12:03:28 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Feb 10 12:03:28 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 12:03:28 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Feb 10 12:03:28 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Fri Feb 10 12:03:28 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Feb 10 12:03:28 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 16:01:04 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Feb 10 16:01:04 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Feb 10 16:01:04 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Feb 10 16:01:04 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 16:01:04 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Feb 10 16:01:04 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Fri Feb 10 16:01:04 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Feb 10 16:01:04 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 20:01:09 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Feb 10 20:01:09 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Feb 10 20:01:09 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Feb 10 20:01:09 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 20:01:09 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Feb 10 20:01:09 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Fri Feb 10 20:01:09 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Feb 10 20:01:09 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 08:12:26 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Feb 11 08:12:29 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Feb 11 08:12:29 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Feb 11 08:12:29 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 08:12:29 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Feb 11 08:12:29 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sat Feb 11 08:12:29 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Feb 11 08:12:29 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 12:02:30 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Feb 11 12:02:30 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Feb 11 12:02:30 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Feb 11 12:02:30 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 12:02:30 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Feb 11 12:02:30 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sat Feb 11 12:02:30 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Feb 11 12:02:30 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 16:01:01 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Feb 11 16:01:01 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Feb 11 16:01:01 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Feb 11 16:01:01 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 16:01:01 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Feb 11 16:01:01 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sat Feb 11 16:01:01 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Feb 11 16:01:01 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 20:00:54 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Feb 11 20:00:55 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Feb 11 20:00:55 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sat Feb 11 20:00:55 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 20:00:55 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Feb 11 20:00:55 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sat Feb 11 20:00:55 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sat Feb 11 20:00:55 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 08:08:52 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Feb 12 08:08:53 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Feb 12 08:08:53 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Feb 12 08:08:53 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 08:08:53 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Feb 12 08:08:53 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sun Feb 12 08:08:53 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Feb 12 08:08:53 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 12:02:37 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Feb 12 12:02:38 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Feb 12 12:02:38 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Feb 12 12:02:38 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 12:02:38 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Feb 12 12:02:38 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sun Feb 12 12:02:38 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Feb 12 12:02:38 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 16:01:04 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Feb 12 16:01:04 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Feb 12 16:01:04 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Feb 12 16:01:04 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 16:01:04 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Feb 12 16:01:04 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sun Feb 12 16:01:04 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Feb 12 16:01:04 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 20:00:58 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Feb 12 20:00:58 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Feb 12 20:00:58 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Sun Feb 12 20:00:58 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 20:00:58 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Feb 12 20:00:58 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Sun Feb 12 20:00:58 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Sun Feb 12 20:00:58 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 08:16:17 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Feb 13 08:16:18 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Feb 13 08:16:18 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Feb 13 08:16:18 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 08:16:18 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Feb 13 08:16:18 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Mon Feb 13 08:16:19 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Feb 13 08:16:19 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 12:02:56 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Feb 13 12:02:56 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Feb 13 12:02:56 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Feb 13 12:02:56 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 12:02:56 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Feb 13 12:02:56 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Mon Feb 13 12:02:56 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Feb 13 12:02:56 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 16:01:17 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Feb 13 16:01:17 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Feb 13 16:01:17 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Feb 13 16:01:17 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 16:01:17 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Feb 13 16:01:17 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Mon Feb 13 16:01:17 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Feb 13 16:01:17 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 20:00:58 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Feb 13 20:00:58 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Feb 13 20:00:58 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Mon Feb 13 20:00:59 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 20:00:59 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Feb 13 20:00:59 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Mon Feb 13 20:00:59 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Mon Feb 13 20:00:59 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 08:18:21 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Feb 14 08:18:22 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Feb 14 08:18:22 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Feb 14 08:18:22 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 08:18:22 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Feb 14 08:18:22 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Tue Feb 14 08:18:23 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Feb 14 08:18:23 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 12:03:12 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Feb 14 12:03:13 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Feb 14 12:03:13 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Feb 14 12:03:13 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 12:03:13 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Feb 14 12:03:13 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Tue Feb 14 12:03:13 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Feb 14 12:03:13 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 16:01:21 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Feb 14 16:01:21 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Feb 14 16:01:21 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Feb 14 16:01:21 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 16:01:21 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Feb 14 16:01:21 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Tue Feb 14 16:01:21 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Feb 14 16:01:21 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 20:01:03 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Feb 14 20:01:03 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Feb 14 20:01:03 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Tue Feb 14 20:01:03 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 20:01:03 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Feb 14 20:01:03 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Tue Feb 14 20:01:03 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Tue Feb 14 20:01:04 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 08:25:40 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 15 08:25:43 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 15 08:25:43 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 15 08:25:43 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 08:25:43 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Feb 15 08:25:43 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Wed Feb 15 08:25:43 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Feb 15 08:25:43 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 12:05:08 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 15 12:05:09 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 15 12:05:09 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 15 12:05:09 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 12:05:09 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Feb 15 12:05:09 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Wed Feb 15 12:05:09 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Feb 15 12:05:09 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 16:01:28 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 15 16:01:28 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 15 16:01:28 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 15 16:01:28 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 16:01:28 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Feb 15 16:01:28 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Wed Feb 15 16:01:28 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Feb 15 16:01:28 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 19:27:59 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 15 19:27:59 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 15 19:27:59 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 15 19:28:00 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 19:28:00 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Feb 15 19:28:00 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Wed Feb 15 19:28:00 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Feb 15 19:28:00 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 20:12:56 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 15 20:12:57 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 15 20:12:57 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Feb 15 20:12:57 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 20:12:57 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Feb 15 20:12:57 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Wed Feb 15 20:12:57 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Wed Feb 15 20:12:57 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 16 08:44:36 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 16 08:44:38 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 16 08:44:38 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 16 08:44:38 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 16 08:44:38 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Feb 16 08:44:38 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Thu Feb 16 08:44:38 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Thu Feb 16 08:44:38 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users > From mal at egenix.com Fri May 9 22:31:13 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Mar 31 16:33:28 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.5 Message-ID: <3EBC0201.9060507@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.5 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.5 introduces the following new features compared to version 1.0.4: * Support for multi-statement queries. Z SQL Methods allow multiple statements in a single query via the feature. mxODBC Zope DA 1.0.5 now supports this feature as well. * Lazy Connect: mxODBC Zope DA 1.0.5 only reconnects mxODBC Connection objects if Zope requests a connection object. This results in better use of available resources. Other Zope DAs tend to always reconnect when loading the connection objects into memory, e.g. when loading the folder containing the connection object, even though the connection is not really used for anything. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Fri May 9 23:05:08 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Mar 31 16:33:28 2006 Subject: [egenix-users] mx incompatabilities In-Reply-To: References: Message-ID: <3EBC09F4.4090807@lemburg.com> [Please subscribe to this list before posting, thanks] Brett Haydon wrote: > I am looking at migrating my ZMysqlDA connections to Zmx.. but I'm having > problems on my test (W2k) Zope 2.6.1 > > I've tracked it down to mx.DateTime clashing with Zope DateTime. > The following PageTemplate code causes Zope to hang with mx modules > installed > " > tal:content="python:DateTime(items.date_submitted).strftime('%d/%m/%Y')"> > 24/04/03 > " What do you mean with "hangs" ? Doesn't Zope generate some kind of error traceback ? Also, are you using the mxODBC Zope DA or the egenix-mx-base package ? (The Zope DA ships with mxDateTime 2.1.0 which should be fully compatible to Zope templates.) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 09 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 46 days left From mal at lemburg.com Tue May 13 01:10:04 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Mar 31 16:33:28 2006 Subject: [egenix-users] mx.DateTime and Glibc 2.3 In-Reply-To: <20030318210623.GB24499@gnubia.net> References: <20030318210623.GB24499@gnubia.net> Message-ID: <3EC01BBC.1030208@lemburg.com> Justin Ryan wrote: > Hello, > > I'm having some trouble with mx.DateTime which I beleive is related to > Glibc v2.3 - however I'm not 100% sure, and would not be able to file a > relevant bug report against glibc without a bit more information. > > Essentially, mx.DateTime is raising an exception with pre-1970 dates > when trying to access a DateTime object's ticks() method. On other > systems, a negative integer is returned. Note that the negative ticks range is mostly undefined, so this is not really a bug in the C lib. Many systems do return negative values for dates before 1970, but some don't and return an error instead (this is what you see under gibc 2.3). > I was able to install debian stable (glibc 2.2), and do ssomething like > the following: > > <- snip -> > > $ python > Python 2.2 (#1, Apr 25 2002, 17:44:12) > [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > -315597600.0 > > > <- snip -> > > I then upgraded my glibc and nothing else, with the following result: > > <- snip -> > > $ python > Python 2.2.2 (#1, Jan 18 2003, 10:18:59) > [GCC 3.2.2 20030109 (Debian prerelease)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>>>from mx.DateTime import DateTime >>>>d = DateTime( 1960 ) >>>>print d > > 1960-01-01 00:00:00.00 > >>>>d.ticks() > > Traceback (most recent call last): > File "", line 1, in ? > mx.DateTime.Error: cannot convert value to a time value > > > <- snip -> > > Because I am not familiar with the c sources to mxdatetime, it's > difficult for me to troubleshoot this. Any help is much appreciated - > even if it is only providing enough information / guidance to file a > relevant report against glibc. > > Thanks in advance, > > -Justin > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at lemburg.com Tue May 13 01:12:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Mar 31 16:33:28 2006 Subject: [egenix-users] RE: Psycopg on Solaris 8 with egenix mxDateTime In-Reply-To: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> References: <0E5DE51569488947A432F0A8F10E4501026A4E94@miholhlex01.usfholland.com> Message-ID: <3EC01C48.3020204@lemburg.com> Cole, Timothy wrote: > Chris, > > > > I was able to discover how to get psycopg to compile on Solaris. It turned > out to be in the egenix mxDateTime module. > > > > Just edit the egenix-mx-base-2.0.4/mx/DateTime/mxDateTimemxDateTime.c file > > > > Comment out these lines around line 80 BEFORE you run "python setup.py > install". > > > > #define MXDATETIME_FREELIST > > #define MXDATETIMEDELTA_FREELIST > > > > like so. > > > > /* #define MXDATETIME_FREELIST*/ > > /* #define MXDATETIMEDELTA_FREELIST */ > > > > Hope this works for you. Sounds like another broken optimizer. gcc3 seems to have lots of these problems. > Complete everything else as instructed in the install's/readme's/etc. > > > > BTW, My environment is as follows. > > > > Solaris 8 on a SunFire 280R > > Zope 2.6.1 > > Postgres 7.3.2 > > Egenix-mx-base 2.0.4 > > Psycopg 1.1.2 > > Gcc 3.2.2 > > Python 2.1.3 > > > > Cheers, > > > > Timothy Cole > > Systems Engineer, Midrange Systems > > > > -----Original Message----- > From: christov@mac.com [mailto:christov@mac.com] > Sent: Thursday, March 06, 2003 2:59 PM > To: Cole, Timothy > Subject: Re: Psycopg on Solaris 8 > > > > Hi Tim, > > > > My target (or at least immediate target) platform turned into Linux, so I > haven't worked on the psycopg issue on Solaris in quite a while. > > > > I recall finding that it was really the mx.DateTime module that was broken > when compiled with gcc 3.x. I think that I rebuilt everything with SunPro cc > 5.0 and it was fine, but I haven't tried anything in months. > > > > Good luck, > > Chris > > > > On Wednesday, Mar 5, 2003, at 20:31 US/Pacific, Cole, Timothy wrote: > > > > Chris, > > > > > > > > Hi, was wondering if you had made any headway on the psycopg on Solaris 8? > I am running into the same problems and haven't been able to make any > forward progress. > > > > > > > > Any help or pointers would be greatly appreciated. > > > > > > > > Cheers, > > > > > > > > Timothy Cole > > > > Systems Engineer, Midrange Systems > > > > USF Technology Services, Inc. > > > > 630 Kenmoor Ave. SE, Suite 200 > > > > Grand Rapids,Michigan49546 > > > > Ph. 616.802.1108 > > > > > > > > > > ------------------------------------------------------------------------ > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 42 days left From mal at egenix.com Wed May 14 23:16:21 2003 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Mar 31 16:33:28 2006 Subject: [egenix-users] ANN: eGenix mxODBC Zope Database Adapter, Version 1.0.6 Message-ID: <3EC2A415.8040401@egenix.com> ________________________________________________________________________ ANNOUNCEMENT EGENIX.COM mxODBC Zope Database Adapter Version 1.0.6 Available for Zope 2.3 - 2.6 on Windows, Linux and Solaris ________________________________________________________________________ INTRODUCTION The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows XP/NT/2000/98/95, Linux and Solaris using the same interface on all platforms. The mxODBC Zope DA implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving a much better performance than ZODBC Zope DA or similar Zope database adapters under heavy load. This makes it ideal for deployment in Zope Clusters and Zope hosting environments where stability and high performance are a top priority. ________________________________________________________________________ FEATURES * Zope Level 3 Database Adapter: the mxODBC Zope DA is fully multi-threaded and can handle multiple connections to multiple databases. * Fully compatible to Z SQL Methods. * Drop-in compatible to the ZODBC DA: the mxODBC Zope DA provides the same interfaces as Zope's ZODBC DA to allow a smooth upgrade path from this simplistic adapater to the high performance mxODBC Zope DA. * Fully compatible to the Znolk SQL Wizard Product and other similar products relying on the common database schema access methods .tables() and .columns(). * Connection Pooling: physical database connections are pooled and kept open, to reduce the connection overhead to a minimum. This is especially important for high latency database connections and ones like Oracle which take a considerable amount of time to setup * Parallel Execution of Queries on a single logical connection: the mxODBC Zope DA can manage any number of physical connections on a single logical connection. This enables running truly parallel Z SQL Method queries -- a feature not available in other Zope DAs. * Robust Mode of Operation: connections which have timed out or go away due to network problems are automatically reconnected. * Cross-platform Connection Objects: The Zope DA will automatically choose the right platform specific ODBC manager for you. * Per Connection Adjustable ODBC Interface: mxODBC comes with many different subpackages to choose from on Unix. The Zope DA allows you to select these subpackages on a per-connection basis. * Per Connection Error Handling: you can tell each connection whether it should report ODBC warnings or not; furthermore all warnings and errors are made available as list .messages on the DatabaseConnection object. * Transaction safe automatic reconnect: when the DA finds that a connection has timed out, it automatically tries a reconnect and replays the transaction on the connection (unlike other DAs which break the transaction scheme by doing a reconnect without replay). * Built-in Schema Cache: this results in improved performance under heavy load. * Database Schema Access: all ODBC catalog methods are made available for much better database schema inquiry. The catalog methods allow building generic database interrogation or manipulation tools and facilitates writing database independent Zope products. * Lazy Connect: the mxODBC Zope DA only connects to the database backends when a connection is actually requested. This results in a better use of resources compared to other Zope DAs. ________________________________________________________________________ NEWS Version 1.0.6 includes the following changes and enhancements: * The lazy connect feature was turned into a per-connection option. This gives you more control over which connections are maintained in connect-on-demand state and which are always connected. * A new option was introduced to let the mxODBC Zope DA return the natively used mxDateTime values instead of converting them to Zope's DateTime instances. This is a faster if you're dealing with a lot of date/time values and also provides more flexibility in data access. See the mxDateTime documentation for full details on what this package can offer. * A bug in the version 1.0.5 lazy connect feature was fixed. In short: mxODBC Zope DA is continuing to become the number one solution for integrating relational databases with Zope applications. ________________________________________________________________________ UPGRADING If you have already bought mxODBC Zope DA licenses, you can use these license for the updated version as well. There is no need to buy new licenses. The same is true for evaluation license users. ________________________________________________________________________ MORE INFORMATION For more information on the mxODBC Zope DA, licensing and download instructions, please visit our web-site: http://www.egenix.com/ You can buy mxODBC Zope DA licenses online from the eGenix.com shop at: http://shop.egenix.com/ ________________________________________________________________________ Thank you, -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From genechow at pacbell.net Thu May 29 11:57:31 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Mar 31 16:33:28 2006 Subject: [egenix-users] DateTimeFrom problem Message-ID: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is easy to work around, but it does not seem correct or desirable. Python 2.1.3 (#1, Aug 29 2002, 17:22:52) [GCC 3.1 20020420 (prerelease)] on darwin6 Type "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> From robinjim at earthlink.net Thu May 29 17:38:13 2003 From: robinjim at earthlink.net (robin and jim) Date: Fri Mar 31 16:33:28 2006 Subject: [egenix-users] DateTimeFrom problem References: <04A3366C-91FF-11D7-9C8D-000502219650@pacbell.net> Message-ID: <001901c32632$ff0083f0$a3b61f43@robinjim> For what it is worth, the behavior is correct with Python 2.2.2 on MS Windows: PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32. Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) - see 'Help/About PythonWin' for further copyright information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> DateTimeFrom('2003-05-28') >>> import mx >>> mx.__version__ '2.0' >>> ----- Original Message ----- From: "Gene Chow" To: Sent: Thursday, May 29, 2003 11:57 AM Subject: [egenix-users] DateTimeFrom problem > I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is > easy to work around, but it does not seem correct or desirable. > > Python 2.1.3 (#1, Aug 29 2002, 17:22:52) > [GCC 3.1 20020420 (prerelease)] on darwin6 > Type "copyright", "credits" or "license" for more information. > >>> from mx.DateTime import DateTimeFrom > >>> DateTimeFrom('2003/05/28') > > >>> DateTimeFrom('2003-05-28') > > >>> > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > http://lists.egenix.com/mailman/listinfo/egenix-users From genechow at pacbell.net Thu May 29 17:38:23 2003 From: genechow at pacbell.net (Gene Chow) Date: Fri Mar 31 16:33:28 2006 Subject: [egenix-users] DateTimeFrom problem In-Reply-To: <001901c32632$ff0083f0$a3b61f43@robinjim> Message-ID: Here's a couple of other setups that produce the wrong answer: Python 2.2 (#1, 07/14/02, 23:25:09) [GCC Apple cpp-precomp 6.14] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> Python 2.2.1 (#1, Apr 18 2002, 09:42:55) [GCC 2.95.3 20010315 (release) [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> from mx.DateTime import DateTimeFrom >>> DateTimeFrom('2003/05/28') >>> import mx >>> mx.__version__ '2.0' >>> On Thursday, May 29, 2003, at 03:38 PM, robin and jim wrote: > For what it is worth, the behavior is correct with Python 2.2.2 on MS > Windows: > > PythonWin 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on > win32. > Portions Copyright 1994-2001 Mark Hammond (mhammond@skippinet.com.au) > - see > 'Help/About PythonWin' for further copyright information. >>>> from mx.DateTime import DateTimeFrom >>>> DateTimeFrom('2003/05/28') > >>>> DateTimeFrom('2003-05-28') > >>>> import mx >>>> mx.__version__ > '2.0' >>>> > ----- Original Message ----- > From: "Gene Chow" > To: > Sent: Thursday, May 29, 2003 11:57 AM > Subject: [egenix-users] DateTimeFrom problem > > >> I'm using egenix-mx-base-2.0.4 on Mac OS X. The following behavior is >> easy to work around, but it does not seem correct or desirable. >> >> Python 2.1.3 (#1, Aug 29 2002, 17:22:52) >> [GCC 3.1 20020420 (prerelease)] on darwin6 >> Type "copyright", "credits" or "license" for more information. >>>>> from mx.DateTime import DateTimeFrom >>>>> DateTimeFrom('2003/05/28') >> >>>>> DateTimeFrom('2003-05-28') >> >>>>> >> >> >> ______________________________________________________________________ >> _ >> eGenix.com User Mailing List >> http://www.egenix.com/ >> http://lists.egenix.com/mailman/listinfo/egenix-users >