From mal at egenix.com Sat Apr 2 03:18:49 2011 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Apr 2 02:19:03 2011 Subject: [egenix-users] Problem with mxodbc 3.1 and Sybase 15.5 In-Reply-To: <4D66B0C8.6090701@uchicago.edu> References: <4D13ABBD.8020705@uchicago.edu> <4D13AF01.7000003@egenix.com> <4D143673.6000609@uchicago.edu> <4D226642.80603@uchicago.edu> <4D23972E.5020608@egenix.com> <4D23AB65.1010604@uchicago.edu> <4D23B5CA.2010607@egenix.com> <4D6551BE.7020405@uchicago.edu> <4D66B0C8.6090701@uchicago.edu> Message-ID: <4D966B69.9000306@egenix.com> Hi Dale, just to keep you updated: we've been trying several different work-arounds to resolve the problem, but none of them have been successful yet - the Sybase ODBC driver keeps returning error messages, or worse, inserts garbled data into the columns that are to receive a NULL value. It may indeed be better to wait for Sybase to fix their driver instead of coming up with some work-around that may well cause problems with future versions of their driver. Alternatively, please try one of the other available ODBC drivers for Sybase, e.g. the EasySoft one for Unix or the drivers from DataDirect or OpenLink. Even the FreeTDS ODBC driver could be used - it is not as robust as the other drivers and doesn't handle Unicode, but it's still worth a try. In any case, we'll keep trying to find a work-around and hoping that one of the Sybase EBFs will eventually fix the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 02 2011) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ Dale Arntson wrote: > Beautiful. Let me know if you want someone to test the changes. > > -dale > > On 2/24/2011 5:20 AM, Charlie Clark wrote: >> Am 23.02.2011, 19:28 Uhr, schrieb Dale Arntson : >> >>> Hi Marc-Andre, >>> Do you have a time-frame for working around the problem in the Sybase >>> 15 ODBC driver which causes None values to be bound to SQL_CHAR? Just >>> asking, so I can plan accordingly. >> >> Hi Dale, >> >> we hope to have a build with this by the end of March. Note, this might >> not be a full release. >> >> Charlie > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users From mal at egenix.com Wed Apr 20 14:40:11 2011 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Apr 20 13:40:15 2011 Subject: [egenix-users] Problem with mxodbc 3.1 and Sybase 15.5 In-Reply-To: <4D966B69.9000306@egenix.com> References: <4D13ABBD.8020705@uchicago.edu> <4D13AF01.7000003@egenix.com> <4D143673.6000609@uchicago.edu> <4D226642.80603@uchicago.edu> <4D23972E.5020608@egenix.com> <4D23AB65.1010604@uchicago.edu> <4D23B5CA.2010607@egenix.com> <4D6551BE.7020405@uchicago.edu> <4D66B0C8.6090701@uchicago.edu> <4D966B69.9000306@egenix.com> Message-ID: <4DAEC61B.2020403@egenix.com> Just to give our users an update: We have been working with Dale to reproduce the problem he was seeing with passing NULL values to the Sybase database, but were not able to reproduce the exact same problem. What we did find was that the Sybase ODBC driver for Linux x64 is broken in that it sends garbage to the database when inserting a NULL value. This is most likely due to a 64-bit related bug in the driver. We were so far not able to find a work-around for this driver bug. The driver simply ignores the ODBC setting for NULLs on 64-bit platforms and copies over the data from an uninitialized buffer. On Linux x86 and Windows x86, the Sybase ODBC driver version 15.5.0.1022 (which is included in the EBFs 18373, 18374, 18375 and 18380 for Sybase ASE 15.5) works fine with NULLs. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 20 2011) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ M.-A. Lemburg wrote: > Hi Dale, > > just to keep you updated: we've been trying several different > work-arounds to resolve the problem, but none of them have been > successful yet - the Sybase ODBC driver keeps returning error > messages, or worse, inserts garbled data into the columns > that are to receive a NULL value. > > It may indeed be better to wait for Sybase to fix their driver > instead of coming up with some work-around that may well cause > problems with future versions of their driver. > > Alternatively, please try one of the other available ODBC drivers > for Sybase, e.g. the EasySoft one for Unix or the drivers from > DataDirect or OpenLink. Even the FreeTDS ODBC driver could be used - > it is not as robust as the other drivers and doesn't handle Unicode, > but it's still worth a try. > > In any case, we'll keep trying to find a work-around and hoping > that one of the Sybase EBFs will eventually fix the problem. > > Thanks, From mal at egenix.com Fri Apr 29 18:23:53 2011 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Apr 29 17:23:56 2011 Subject: [egenix-users] mxODBC Zope DA: pinning the 2.0 version Message-ID: <4DBAD809.1070500@egenix.com> Dear Users of our mxODBC Zope DA, we are currently working on the release 2.1 of the Zope DA which will update the included mxODBC from version 3.0 to 3.2 and thus make it compatible with current versions of DB ODBC drivers as well as add support for Netezza, Terradata and the DataDirect ODBC manager. It will also switch over to unixODBC 2.3.0 on Unix, which is esp. important for 64-bit platforms, since EasySoft changed an internal data type. Since most of you are using zc.buildout for installing the Zope DA, it is important to pin down the latest version of the mxODBC Zope DA 2.0 which is "2.0.1" in your [versions] section or versions.cfg file of the buildout setup. If you don't have an entry for egenix-mxodbc-zopeda (the egg package name of the Zope DA), please add a line as follows: egenix-mxodbc-zopeda = 2.0.1 Not doing to would otherwise cause zc.buildout to pick up the new 2.1.0 version once we release it, causing the product to fail due to the installed license being incompatible with new version. We don't have a definite release date yet, but the release should be ready in about 2-3 weeks. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2011) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2011-06-20: EuroPython 2011, Florence, Italy 52 days to go ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/